Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-3611 4.2-testsuite on RHEL4 (sun jdk5)
  3. JBAS-4247

failing org.jboss.test.messagedriven.test.JMSContainerInvokerQueueMessageDrivenUnitTestCase

    XMLWordPrintable

Details

    Description

      testRestartJMS
      Error Cannot send a message to the JMS server; - nested throwable: (java.io.IOException: Client is not connected)
      org.jboss.mq.SpyJMSException: Cannot send a message to the JMS server; - nested throwable: (java.io.IOException: Client is not connected)
      at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
      at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57)
      at org.jboss.mq.Connection.sendToServer(Connection.java:922)
      at org.jboss.mq.SpySession.sendMessage(SpySession.java:924)
      at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:272)
      at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:206)
      at org.jboss.test.messagedriven.support.SendMessageOperation.run(SendMessageOperation.java:50)
      at org.jboss.test.messagedriven.support.BasicMessageDrivenUnitTest.runTest(BasicMessageDrivenUnitTest.java:112)
      at org.jboss.test.messagedriven.test.JMSContainerInvokerQueueMessageDrivenUnitTestCase.testRestartJMS(JMSContainerInvokerQueueMessageDrivenUnitTestCase.java:67)
      Caused by: java.io.IOException: Client is not connected
      at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264)
      at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:220)
      at org.jboss.mq.il.uil2.UILServerIL.addMessage(UILServerIL.java:245)
      at org.jboss.mq.Connection.sendToServer(Connection.java:918)
      ... 21 more

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue JBAS-4222 Add support for stopping ILs triggering the ExceptionListener - UIL2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              adrian.brock Adrian Brock (Inactive)
              dandread1@redhat.com Dimitrios Andreadis
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: