Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-1331

Could not stop JMS connection

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBossAS-4.0.2RC1
    • JBossAS-4.0.1 Final
    • JMS (JBossMQ)
    • None

      Sometimes my JBoss client will lose its connection to the server and it gets into a never-ending loop of spewing errors because Connection.doStop throws an exception. The stack trace looks like this:

                    • ERROR Jan 26 08:53:25 [plugins.jms.JMSContainerInvoker] - Could not stop JMS connectionorg.jboss.mq.SpyJMSException: Cannot disable the connection with the JMS server; - nested throwable: (java.io.IOException: Client is not connected) at org.jboss.mq.Connection.doStop(Connection.java:1289) at org.jboss.mq.Connection.stop(Connection.java:718) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStop(JMSContainerInvoker.java:876) at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1316) at java.lang.Thread.run(Thread.java:595)Caused by: java.io.IOException: Client is not connected at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:232) at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:200) at org.jboss.mq.il.uil2.UILServerIL.setEnabled(UILServerIL.java:189) at org.jboss.mq.Connection.doStop(Connection.java:1285) ... 4 more

      This error occurs every 2 minutes until I restart the server. I patched Connection.java inside doStop to just log a warning if the call to serverIL.setEnabled throws an exception instead of wrapping it in a JMSException and rethrowing it.

            adrian.brock Adrian Brock (Inactive)
            javajedi_jira Tim McCune (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: