Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.rmi.NoSuchObjectException: RemoteInvokable

2 views
Skip to first unread message

Lee Latimer

unread,
Apr 20, 2002, 11:37:56 AM4/20/02
to
What's the deal on this error... is it related to
<Server
DGCIdlePeriodsUntilTimeout=10
/>

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>>

Kawaljit Singh Sunny

unread,
Apr 21, 2002, 12:00:47 AM4/21/02
to
This can only happen in JMS subsystem if you have a cluster configuration on
6.1
and is a known issue and you can open a case with BEA.
This has been fixed for JMS in 7.0.

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...

0 new messages