AFAIK you should use SpyQueue for this.
The Queue is not realy deployed at this server with JBoss4.2 the JBossMQ is the JMS provider and this is a HA-Singleton (only one JBoss start the JBossMQ component).
Is there a reason to use 4.2? With 4.3 the problem is solved because here the JBossMessaging is the JMS provider (full cluster aware).
The only difference between 4.2 and 4.3 is JMS and WebServices.
thanks for the fast response!
indeed we have to stick to 4.2.2 because of compatability issues with some of the legacy apps. We tested 4.3 but it didn't seem to handle very stable.
We will look for some alternative solutions like ActiveMQ but I would have been pretty happy if we could set up HA Jndi solutions, so that each node finds the queue on the current master node. I will have a look at SpyQueue as well, thanks again.
Also a solution can be to use JBM with JBoss 4.2
There are some instructions on how to deploy JBoss Messaging in JBoss AS 4.2.x in the JBoss Messaging user guide.
Huge thanks for the help mate. Managed to configure the jboss messaging, both servers can send successully now. Only thing is the clustering is not doing round robin as expected and when one server goes down the messages it had to send are not given to the other. I guess this is configuration problem, will figure it out hopefully.
Alternative my collegues offered to use ActiveMQ, it could be a nice solution as well, need to try it out.