JMS Exception DisconnectMonitor timed out after 299s.

Question

Hi,
Could anone please suggest regarding below exception and the parameter which can be configured for this timeout in JMS.
Thanks,
JMS exception class = java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
weblogic.jms.common.LostServerException: java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
     at weblogic.jms.client.JMSConnection.dispatcherPeerGone(JMSConnection.java:1436)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:692)
     at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:617)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.ExecuteThreadLite.execute(ExecuteThreadLite.java:72)
     at weblogic.work.ExecuteThreadLite.run(ExecuteThreadLite.java:56)
Caused by: java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
     at weblogic.messaging.dispatcher.DispatcherWrapperState.onDisconnect(DispatcherWrapperState.java:396)
     at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate.deliverDisconnectEvent(AbstractDisconnectMonitorDelegate.java:156)
     at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate.access$400(AbstractDisconnectMonitorDelegate.java:25)
     at weblogic.rmi.extensions.AbstractDisconnectMonitorDelegate$Timer.run(AbstractDisconnectMonitorDelegate.java:234)
     at java.lang.Thread.run(Unknown Source)

Answer 1

Hi,
The Error message :
JMS exception class = java.lang.Exception: weblogic.rmi.extensions.DisconnectMonitorException: DisconnectMonitor timed out after 299s.
Indicates that the server hosting the remote JMS resource has been disconnected and a Disconnection error message has been delivered to the JMS resource listerners.
This can happen due to following reasons:
1: The network connection has gone down in such a way that only Weblogic's internal heartbeat mechanism manages to detect the problem. Among other possibilities, this can be due to a hardware failure, server crash, or even an overly enthusiastic firewall.
2: You have a slow network connection and are receiving a very large message, so Weblogic's internal heartbeats fail to get through (they end up queued up behind the large message).
This causes Weblogic to think the connection is lost even though it is actively receiving packets.
you can try increasing the following JMS property values:
Click on the Name of the server (On which you have deployed your application and queues etc...)in the left Pane
Goto --> Protocols-->General--> Advanced Options
Increase the following Parameters
Complete Message Timeout:
Idle Connection Timeout:
Maximum Message Size:
Thanks,
Sandeep