or is it something else ?
Start server side stack trace:
java.rmi.NoSuchObjectException: RemoteInvokable - id: '744'
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:609)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
1) Are you using 6.1? and what Service Pack are you at.
2) Please confirm if you have a cluster configuration.
3) If you can also post the full exception it will be of help.
4) Does this happen when using JMS or some other part of Weblogic Subsystem?
For the time being as a workaround (if and only if you are using JMS) you
can set
DGCIdlePeriodsUntilTimeout to a higher value which will delay this.
Kawaljit Singh Sunny
"Lee Latimer" <l...@latimer.com> wrote in message
news:3cc18b54$1...@newsgroups2.bea.com...