I've just come back to this today and upgraded to JBoss Messaging 1.4.5.GA and
it all runs with no problem.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263531#4263531
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=42
1.5.6 GA is what I'm using.
Producers seem to be failing over OK but not Consumers. Does this provide any
clues? Can you recommend any debug/logging settings that might help to find
the problem?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256455#4256455
Thank you for your very prompt response!
I believe I have already resolved the classpath issue with respect to
jboss-remoting.jar by removing the remoting classes from jbossall-client.jar
(this appears to be the recommended solution in Tomcat where it is otherwise
difficult to control classpath
I am seeking clarification that JBoss Messaging 1.4.4.GA and JBoss AS 4.2.3.GA
are fully compatible and that client failover is fully operational with this
combination.
I have a two node JBoss AS 4.2.3.GA cluster configured in accordance with the
instructions in the JBoss Messaging 1.4.4.GA use
Yes. Include the jars required for any JBoss JMS client.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256396#4256396
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256396
_