MDB listening to multiple HQ instances

[vmeghraj]

Can we make MDB listen to 2 or more non-clustered HQ instances for the destination with same name? Pl clarify.

[clebert.suconic]

I can't really understand the question here.

But please, look at the documentation, and specially the examples about JCA connecting remotely to other instances.

It should be easy as reading the doc here.

[vmeghraj]

Clebert, thank you for your response. Sorry for not being clear with my query. I want my MDB to consume messages from 2 non-clustered HQ instances running on 2 different nodes. The destination (Queue) name is same on both the instances. How can I achieve this? I hope this is clear.

[ataylor]

Veeru M wrote:

Clebert, thank you for your response. Sorry for not being clear with my query. I want my MDB to consume messages from 2 non-clustered HQ instances running on 2 different nodes. The destination (Queue) name is same on both the instances. How can I achieve this? I hope this is clear.

no thats not possible, and seems like a strange thing to wan to do. 2  clustered nodes yes but not un clustered. What is your use case?

[clebert.suconic]

you always connect to a single node on JMS.

(Actually on any messaging provider existent out there).

And you may have clustering at the server side.

what you ask doesn't make much sense to me.

[vmeghraj]

We have a scenario where the messages are produced from 2 different environments, but to the same destination queue. The messages produced from different app server environments land in HQ instances on different nodes. The MDB living in JBoss is the only consumer responsible for processing those messages. Due to operational reasons, it is not possible for us to make these 2 different environments to drop the messages to same HQ instance.

We were hoping to have a solution something similar to client side load balancing.

[clebert.suconic]

It sounds like peer to peer to me. It's a feature request ATM:

https://jira.jboss.org/browse/HORNETQ-87

I believe you would able to achieve that with bridges. Or clustering without UDP ( as explained on the manual )

[timfox]

I think what the user is asking does make sense.

It should be achievable by deploying the same MDB twice with two different sets of resource adaptor settings pointing at two different servers