I'm not personally familiar with the details of this aspect of JBossMQ, but your analysis sounds correct.
A workaround: | <message-driven> | <ejb-name>ContatoConsumerBean</ejb-name> | <configuration-name>Standard Message Driven Bean</configuration-name> | <destination-jndi-name>queue/cadastro</destination-jndi-name> | | <mdb-user>${ContatoConsumerBean.mdb.user:CadastroUser}</mdb-user> | <mdb-passwd>CadastroUser</mdb-passwd> | <mdb-subscription-id>CadastroUser</mdb-subscription-id> | | </message-driven> | then start JBoss like this: ./run.sh -DContatoConsumerBean.mdb.user=$CADASTRO_USER_ID -c all Then on each server you'd use a different value for the $CADASTRO_USER_ID environment var. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146913#4146913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146913 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user