Same problem here. Does anyone has a solution for this problem (3.2.5)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848397#3848397
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848397
--
Hi!
Yes, I've got a "workaround" on this.
As you can see, this is an expected behaviour since JBoss 3.2.4:
http://jboss.org/wiki/Wiki.jsp?page=JBossMQHA
On option to make the service "activate" before the servers synchronizes state (wich
takes 1 minute to happen after the master node crashes)
Hi folks,
Have you had any resolution on this? We're experiencing the same problem in that our
queues depend on the DestinationManager which apparently only starts up on the master
node.
How are the other nodes in the cluster aware of the various jms-queues if this is the
case?
I'm convinced
Hi!
I'm getting the same behaviour as you may see in my post.
I believe this happens to guarantee that only one instance consumes the messages but
I'd like to confirm this.
Did you get any new info about it?
Daniel
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtop
