[java.rmi.NoSuchObjectException: RemoteInvokable

Rajeev Karri

unread,

Feb 5, 2002, 5:31:35 PM2/5/02

to

The following stack trace is seen from a QueueReceiver.receive function call. There
is a server side stack trace, but the Weblogic JMS server is up (the queues are
monitorable on the administration console, after this exception is seen).
Any ideas for the reason behind the exception below ?

2002-02-05 12:22:18,507 [Thread-23] ERROR integration.adapter.AdapterTransaction
-Exception while trying to process transaction
java.rmi.NoSuchObjectException: RemoteInvokable - id: '395'

Start server side stack trace:
java.rmi.NoSuchObjectException: RemoteInvokable - id: '395'
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

at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:134)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:341)
at weblogic.jms.client.JMSSession.commit(JMSSession.java:490)
at com.yantra.interop.services.jms.JMSConsumer.acknowledgeSuccess(JMSConsumer.java:99)
at com.yantra.interop.services.jms.JMSCallback.acknowledgeMessage(JMSCallback.java:85)
at com.yantra.integration.adapter.AdapterTransaction.completeTransaction(AdapterTransaction.java:186)
at com.yantra.integration.adapter.AdapterTransaction.execute(AdapterTransaction.java:144)
at com.yantra.integration.adapter.IntegrationAdapter.onMessage(IntegrationAdapter.java:219)
at com.yantra.interop.services.jms.JMSContextMediator.processMessage(JMSContextMediator.java:104)
at com.yantra.interop.services.jms.JMSConsumer.onMessage(JMSConsumer.java:120)
at com.yantra.interop.services.jms.JMSConsumer.run(JMSConsumer.java:204)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[java.rmi.NoSuchObjectException: RemoteInvokable - id: '395'

Start server side stack trace:
java.rmi.NoSuchObjectException: RemoteInvokable - id: '395'
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
]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy2.dispatchSyncNoTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:341)
at weblogic.jms.client.JMSSession.commit(JMSSession.java:490)
at com.yantra.interop.services.jms.JMSConsumer.acknowledgeSuccess(JMSConsumer.java:99)
at com.yantra.interop.services.jms.JMSCallback.acknowledgeMessage(JMSCallback.java:85)
at com.yantra.integration.adapter.AdapterTransaction.completeTransaction(AdapterTransaction.java:186)
at com.yantra.integration.adapter.AdapterTransaction.execute(AdapterTransaction.java:144)
at com.yantra.integration.adapter.IntegrationAdapter.onMessage(IntegrationAdapter.java:219)
at com.yantra.interop.services.jms.JMSContextMediator.processMessage(JMSContextMediator.java:104)
at com.yantra.interop.services.jms.JMSConsumer.onMessage(JMSConsumer.java:120)
at com.yantra.interop.services.jms.JMSConsumer.run(JMSConsumer.java:204)
at java.lang.Thread.run(Thread.java:484)

Sasikanth

unread,

Feb 6, 2002, 9:49:55 AM2/6/02

to

Could you tell me more about your environment like your weblogic server version,
service pack number, and also is it reproducible with any particular scenario,
if so describe when exactly you are getting it.

Zach

unread,

Feb 6, 2002, 1:43:18 PM2/6/02

to

This is posted somewhere else in this newsgroup. You need to adjust your
DGC and/or heartbeat intervals. I forget how. Search the news group for
the exception.
_sjz.

"Rajeev Karri" <rka...@yantra.com> wrote in message
news:3c605d47$1...@newsgroups.bea.com...

Sasikanth

unread,

Feb 6, 2002, 4:44:22 PM2/6/02

to

HI

If you can open a case with BEA Customer Support with full details we can
help you to get a patch which I found close to your problem if your weblogic server
version is 6.0

regards
Sasikanth

Sasikanth

unread,

Feb 7, 2002, 12:58:11 PM2/7/02

to

HI

I am Sorry there was a typo in my previous mail. You can open a case with
full details, There is a patch for the problem,
I guess that will fix you that.

regards
Sasikanth