Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10053

Chatroom example ftest fails if deployed after creating JMS topic

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • EAP_EWP 5.2.0 ER2
    • Seam2
    • None
    • RHEL6 x86_64, JDK 1.7.0_05, Seam 2.2.6.EAP5, JBoss EAP 6.0.1 ER 2

    • Hide
      1. Start JBoss EAP 6.0.1.ER2
      2. Create JMS topic with
        $JBOSS_DIR/bin/jboss-cli.sh "connect,jms-topic add --topic-address=testTopic --entries=topic/chatroomTopic"
      3. Build and deploy the migrated remoting/chatroom example to EAP6
      4. Run the tests
        ant -f ${SEAM_DIR}/src/test/ftest/build.xml -Dtest=remoting/chatroom -Dcontainer=jboss5 test.single.example
      Show
      Start JBoss EAP 6.0.1.ER2 Create JMS topic with $JBOSS_DIR/bin/jboss-cli.sh "connect,jms-topic add --topic-address=testTopic --entries=topic/chatroomTopic" Build and deploy the migrated remoting/chatroom example to EAP6 Run the tests ant -f ${SEAM_DIR}/src/test/ftest/build.xml -Dtest=remoting/chatroom -Dcontainer=jboss5 test.single.example
    • NEW

      The remoting/chatroom ftest fails in connectAndChatTest test, if it is deployed after the JMS topic is created. The server log shows javax.jms.IllegalStateException: Connection is closed.

      Note: In reverse order (deploy chatroom, create JMS topic, test) this problem does not manifest.

      13:37:10,326 ERROR [org.jboss.seam.remoting.messaging.SubscriptionRegistry] (http-localhost/127.0.0.1:8080-3) javax.jms.IllegalStateException: Connection is closed
      13:37:10,329 ERROR [org.jboss.seam.remoting.Remoting] (http-localhost/127.0.0.1:8080-3) Error: java.lang.NullPointerException
      	at org.jboss.seam.remoting.messaging.SubscriptionRequest.marshal(SubscriptionRequest.java:31) [jboss-seam-remoting.jar:2.2.6.EAP5]
      	at org.jboss.seam.remoting.SubscriptionHandler.marshalResponse(SubscriptionHandler.java:107) [jboss-seam-remoting.jar:2.2.6.EAP5]
      	at org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:96) [jboss-seam-remoting.jar:2.2.6.EAP5]
      	at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) [jboss-seam-remoting.jar:2.2.6.EAP5]
          ...
      
      13:37:10,344 INFO  [org.jboss.as.ejb3] (http-localhost/127.0.0.1:8080-1) JBAS014101: Failed to find SFSB instance with session ID {[-74, -59, 30, 37, 82, 52, 70, 109, -77, -52, 125, 65, -26, -62, -38, 0]} in cache
      13:37:10,344 ERROR [org.jboss.as.ejb3.invocation] (http-localhost/127.0.0.1:8080-1) JBAS014134: EJB Invocation failed on component ChatRoomAction for method public abstract boolean org.jboss.seam.example.remoting.chatroom.ChatRoomActionWebRemote.connect(java.lang.String): javax.ejb.EJBException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: topicPublisher
      	...
      Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: topicPublisher
      	...
      Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.jms.topicSession
      	...
      	at org.jboss.seam.jms.ManagedTopicPublisher.create(ManagedTopicPublisher.java:53) [jboss-seam.jar:2.2.6.EAP5]
      	...
      Caused by: java.lang.RuntimeException: exception invoking: create
      	...
      Caused by: javax.jms.IllegalStateException: Connection is closed
      	at org.hornetq.jms.client.HornetQConnection.checkClosed(HornetQConnection.java:593)
      	at org.hornetq.jms.client.HornetQConnection.createTopicSession(HornetQConnection.java:386)
      	at org.jboss.seam.jms.TopicSession.create(TopicSession.java:38) [jboss-seam.jar:2.2.6.EAP5]
      	...
      
      

              mnovotny@redhat.com Marek Novotny
              rsmeral Ron Šmeral (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: