HornetQ 2.2.5.Final - MDB not consuming messages properly from queues in a 3-node JMS standalone-server cluster

[mayukh2006]

I have a 3-node cluster of standalone hornetq messaging servers (V 2.2.5.Final) on one of my machine and a queue with the same jndi name "queue/jmsLoggerQueue" on each of the 3 servers.

I connect to one of the queues through JNDI and pass 5 messages which gets distributed in round-robin fasion among the queues.

I have verified this using jconsole and also Hermes JMS queue browser.

Please note that none of the queues have any consumers associated with them yet

Next I start my JBoss server (6.0.0.Final version) on another machine (please note that I upgraded the hornetq version in JBoss 6 from 2.1.2 to 2.2.5 before firing up the server). I already have a message-driven bean defined and deployed , which is supposed to consume messages from "queue/jmsLoggerQueue" from all the 3 hornetq servers (running on the first machine)

But after the server fires up and the MDB is deployed, it ends up consuming message only from one queue, which is on server with a JNDI jnp port of 1099 (FYI - the jnp ports for the other 2 hornetq servers in the cluster are 2099 and 3099)

It does not consume any message from the other 2 queues on the remaining 2 servers in the cluster.

This does not happen if I fire up my JBoss server first and send message to the queues, only after the JBoss server has started up and the MDB properly deployed!!!!!!!!!!!!!

My ra.xml file on JBoss FYI (only the portion I have changed from the default)

<resourceadapter-class>org.hornetq.ra.HornetQResourceAdapter</resourceadapter-class>

      <config-property>

         <description>

            The transport type. Multiple connectors can be configured by using a comma separated list,

            i.e. org.hornetq.core.remoting.impl.invm.InVMConnectorFactory,org.hornetq.core.remoting.impl.invm.InVMConnectorFactory.

         </description>

         <config-property-name>ConnectorClassName</config-property-name>

         <config-property-type>java.lang.String</config-property-type>

         <config-property-value>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</config-property-value>

      </config-property>

      <config-property>

         <description>The transport configuration. These values must be in the form of key=val;key=val;,

            if multiple connectors are used then each set must be separated by a comma i.e. host=host1;port=5445,host=host2;port=5446.

            Each set of params maps to the connector classname specified.

         </description>

         <config-property-name>ConnectionParameters</config-property-name>

         <config-property-type>java.lang.String</config-property-type>

         <config-property-value>host=167.16.187.96;port=5445,host=167.16.187.96;port=6445,host=167.16.187.96;port=7445</config-property-value>

      </config-property>

Any idea as to why this is happening?

[mayukh2006]

Another funny thing is I have NOT set the parameter forward-when-no-consumers explicitly in my hornetq-configuration xml file - which means (the

default value of this parameter is false as per hornetq user manual), all my messages should only go to the first node only, which my client connects to.

But still hornetq distributes the messages to namesake queues on the other nodes in the cluster, although they have no consumers.

Can this be the root cause for the above issue? I have just thinking out loud hear.....I may be wrong.....

/Ray

Updated

Nops......setting the parameter forward-when-no-consumers to true explicitly does not solve the problem either....the MDB still keeps consuming message from the queue on one node only......

[ataylor]

currently MDB's will only connect to one node and consume form it. your messages are load balanced because there are no cunsumers at all, when you start the mdb first all messages are routed to the node that has the consumer so this works. take a look at redistribution, this basically redistributes messages already sent to queues if the queue has no consumers, redistributionDelay on address settings.

[mayukh2006]

Thanks for the response..it worked!!!

When you have a deadline hanging over your head, sometimes you rush through things (that including the user manual) and end up asking dumb questions.....that's what happened here I guess.......

But still I am not clear about the MDB behavior - "currently MDB's will only connect to one node and consume form it"

That's not what I observed - if you deploy your MDB before sending messages to the queues, it consumes messages from all the 3 queues (and there is no redistribution, since I had not set this parameter previously, which means it is set to default value of -1 - that implies no redistribution whatsoever)

Thanks anyways for the reply!

/Ray

[ataylor]

But still I am not clear about the MDB behavior - "currently MDB's will only connect to one node and consume form it"

Mdb's are deployed in pools, default is 15, what im saying is that they will all consume from the same node.