Hi JB,
I'm already using network of brokers with failover URI.
Assuming, I've 2 nodes in my cluster with IPs - ip1 & ip2 respectively,
then the broker URL used by me is
failover:(tcp://ip1:61716, tcp://ip2:61716)?initialReconnectDelay=100
AFAIK, conduit subscription is by default set to true for network of
brokers. Pl. correct me if my this understanding is not correct.
My issue is -
I've one J2EE application having an MDB deployed to both the nodes for HA
solution. Both of them are listening to the same topic. I use the above
broker URL for getting the topic connection. Once a message arrives onto
the topic, I noticed the same message is received by both the consumers
which in fact are the same J2EE application deployed in 2 different nodes
receiving the same message.
I do not want this behaviour because both of the J2EE application does the
same CRUD operation on DB upon receiving the message. If both of them
receives the same message, then essentially they would be trying to do the
same CRUD operation in DB which is unnecessary.
My requirement is J2EE application deployed in 1st node only receives the
message from the topic & does the CRUD in DB but for some reason if this
J2EE application is down, then the message is sent to the J2EE application
deployed in the 2nd node.
_Sanjit
On Sat, Jul 19, 2014 at 9:16 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:
> Hi Sanjit,
>
> if you use a network of brokers, you can use failover URI on the network
> connector, if you enable conduit subscription, the message will be sent to
> one broker, and only fallback to the second one if the first one is down.
>
> Regards
> JB
>
>
> On 07/18/2014 11:25 PM, Sanjit Mohanty wrote:
>
>> Hi,
>> I've topic message listeners running in both the nodes of a cluster.
>> Both of them are listening onto the same topic.
>>
>> But my requirement is I want only one of the message listener should
>> consume the message & only when it's node goes down for some reason, only
>> then the other message consumer takes over & continue processing the
>> messages from the topic.
>>
>> How can I achieve this in activemq? I'm using the activemq version 5.7.0
>>
>> Thanks in advance,
>> Sanjit
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
