DEBUG [1] (01/27/03 10:18:47:500):
ConExceptionHandler->onException::Connection to JMS Server is down...
EXCEPTION [1] (01/27/03 10:18:47:500):
weblogic.jms.common.LostServerException:
weblogic.rjvm.PeerGoneEvent[source=weblogic.rjvm.RJVMImpl@b6cca - id:
'-3987512406289988494S:weblogic2.prescientmarkets.com:[7011,7011,7012,7012,7011,7012,-1]:fundingdesk:server1'
connect time: 'Mon Jan 27 10:13:46 EST 2003'] - id:
'-3987512406289988494S:weblogic2.prescientmarkets.com:[7011,7011,7012,7012,7011,7012,-1]:fundingdesk:server1',
reason: 'weblogic.rjvm.PeerGoneException: No message was received for:
'240' seconds':
PFSConExceptionHandler->handleJMSConnectionException::Got PFS message
connection exception
weblogic.jms.common.LostServerException:
weblogic.rjvm.PeerGoneEvent[source=weblogic.rjvm.RJVMImpl@b6cca - id:
'-3987512406289988494S:weblogic2.prescientmarkets.com:[7011,7011,7012,7012,7011,7012,-1]:fundingdesk:server1'
connect time: 'Mon Jan 27 10:13:46 EST 2003'] - id:
'-3987512406289988494S:weblogic2.prescientmarkets.com:[7011,7011,7012,7012,7011,7012,-1]:fundingdesk:server1',
reason: 'weblogic.rjvm.PeerGoneException: No message was received for:
'240' seconds'
at
weblogic.jms.client.JMSConnection.jmsPeerGone(JMSConnection.java:654)
at
weblogic.jms.dispatcher.DispatcherWrapperState.peerGone(DispatcherWrapperState.java:435)
at weblogic.rjvm.RJVMImpl$PeerGoneDeliverer.execute(RJVMImpl.java:1053)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
srini
Note that the problem is unrelated to JMS per se, it is
the underlying WebLogic to WebLogic connection that is
timing out. (The JMS connection is layered on top
of the WebLogic to WebLogic "rjvm" connection.)
Tom