2 Replies Latest reply on Jul 8, 2010 8:52 AM by huma

    Problem stopping the HornetQ server after finishing the tests

    huma

      Hi all!

       

      I'm having a problem stopping the HornetQ after executing a test.

      The problem occurs on a specific test.

      After the test finishes and when I tell spring framework to destroy the context.

       

      Brief overview of the environment,

      1. I'm embedding HornetQ 2.1.1.Final in an osgi bundle
      2. I'm using spring framework to configure and start the HornetQ server
      3. Tests are run with TestNG

       

      Description of the test:

      1) 2 HornetQServers (clustered)

      2) Test sends 1000 messages to a topic and each MessageConsumer associated to his server receives 1000 messages.

       

      Stacktrace:


      SEVERE: Failed to call listener

      java.lang.IllegalStateException: Cannot find queue info for queue 05f492ec-eec4-4519-abe5-c82c2e54401b122bd850-89ea-11df-b80b-005056c00008
      at org.hornetq.core.postoffice.impl.PostOfficeImpl.onNotification(PostOfficeImpl.java:276)
      at org.hornetq.core.server.management.impl.ManagementServiceImpl.sendNotification(ManagementServiceImpl.java:677)
      at org.hornetq.core.postoffice.impl.PostOfficeImpl.removeBinding(PostOfficeImpl.java:504)
      at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.removeBinding(ClusterConnectionImpl.java:747)
      at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doBindingRemoved(ClusterConnectionImpl.java:735)
      at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:562)
      at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:823)
      at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46)
      at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:941)
      at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:96)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:637)

       

      My question are:

      1. why is this message happening only when I'm executing in cluster environment ?
      2. Could you give me some clue about why is this happening ?
      3. And how can I fix this ?

       

      If you need more information, please just ask for it.

       

      Thank you in advance.

       

      Best Regards

       

      Hugo Marcelino