I know little about configuring JBoss ESB to use HornetQ - that would be a question for the JBoss ESB team.

Regarding clustering in HornetQ - did you successfully run the clustering examples?

Also the logs you posted show JBoss Application server clustering - this is nothing to do with HornetQ clustering.

Having said that, I think I can see a bug.

Looks like a message was sent to a node in the cluster, then distributed internally to other node in the cluster, then forwarded to a client, which then resent the same message back to a server, prompting the error.

Looks like one of the internal clustering errors isn't being removed when a message is delivered to a client.

Can you file a JIRA, and someone will take a look?

Can you replicate this without JBossESB? The HornetQ team won't debug ESB code.

Also please post your test application and configuration, and explain what you expected to see, and what you actually aw.

auth.gabor wrote:

 

No, I can't replicate this without ESB, because I don't know the JBossESB what did do exactly.

 

 

The ESB service creates at least one pair of queue: one for a request messages and another one for a reply messages. The ESB service receives a request message from a (for example) "SimpleServiceRequest" queue, process it, and puts a response message to the "SimpleServiceRequest_reply" queue. The ESB client puts it own message into the "SimpleServiceRequest" queue and wait for reply on the "SimpleServiceRequest_reply" queue.

 

But...

 

I have installed a HornetQ 2.0.0.GA into a JBossAS 5.1.0.GA (without ESB) on two RHEL 5.4 Linux machines as I've read in the documentation, I've started the 'all-with-hornetq' server on these two machines and I've run these small applicaton:

      InitialContext ic = new InitialContext();
      Queue queue = (Queue) ic.lookup("/queue/TestQueue");
      ConnectionFactory qcf = (ConnectionFactory) ic.lookup("java:/XAConnectionFactory");
      Connection connection = qcf.createConnection();
      Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);

       String hostname = InetAddress.getLocalHost().getHostName();
      Boolean isProducer = "node1".equals(hostname);
      if (isProducer)
      {
        connection.start();
        MessageProducer producer = session.createProducer(queue);
        TextMessage message = session.createTextMessage("This is text message" + new Date().getTime());
        producer.send(message);
        connection.close();
      } else
      {
        connection.start();
        MessageConsumer consumer = session.createConsumer(queue);
        TextMessage message = (TextMessage) consumer.receiveNoWait();
        if (message != null)
        {
          perfLogger.doLogInfo("Got message: '%1$s'", message.getText());
        } else
        {
          perfLogger.doLogInfo("No message in the queue");
        }
        connection.close();
      }

 

The consumer on the node2 don't receive messages what the producer creates in the node1. The JBossAS and HornetQ configuration is default install, I've created only a TestQueue queue on two node in the hornetq-jms.xml, I've started a JBossAS cluster with `/opt/jboss/bin/run.sh -b 0.0.0.0 -c all-with-hornetq` command line on each node.

 

Gábor Auth

Firstly, the HornetQ team won't know what ESB does either. You need to contact the ESB team for that.

A few other observations:

Why are you using XAConnectionFactory? You aren't using XA so you should just use /ConnectionFactory

Secondly receiveNoWait will only return a message if one is *immediately available in the queue*. There is no guarantee that the message has reached the second node yet.

Thirdly, see what you have set routeWhenNoConsumers to in your cluster connection config.

The reason your application is not working as you expect, is because when you send the message there are no consumers on any nodes, so your message just remains on the first node.

You then create the consumer on the second node, but the message is not on the second node, so it won't be consumed.

If you created the consumer *before* you sent the message, you would receive it.

If you want messages to be automatically distributed to other nodes when you nedd to enable "message redistribution", by default this is not enabled- this is discussed in the user manual, clustering chapter.

I suggest you read the user manual, especially the parts about "cluster connections", "load balancing" and "message redistribution".