[jboss-user] [Clustering/JBoss] - Re: login/client id that is already connected/cluster config

2008-04-25 Thread maralcbr
Hi, I searched a lot this forum, the spec and the net, but could not find a solution to my problem. I have two JBoss 4.2.2GA running in a cluster. I have an application that deploy a queue in jboss.xml like this: message-driven | ejb-nameContatoConsumerBean/ejb-name |

[jboss-user] [Clustering/JBoss] - Re: login/client id that is already connected/cluster config

2008-04-25 Thread maralcbr
I have more information from my tests. If I shutdown the first server, the error stops happening on the second one. The conclusion I can get is that the MDBs from both servers are acessing the queue on the first loaded node - what is correct. As the JMS service is HA singleton. With this

[jboss-user] [Clustering/JBoss] - Re: login/client id that is already connected/cluster config

2008-04-25 Thread [EMAIL PROTECTED]
I'm not personally familiar with the details of this aspect of JBossMQ, but your analysis sounds correct. A workaround: | message-driven | ejb-nameContatoConsumerBean/ejb-name | configuration-nameStandard Message Driven Bean/configuration-name |