Yes, JBM 1.4.4.GA works with AS 4.2.3.GA.
You need to pay attention to jbossall-client.jar. Make sure jboss-messaging-client.jar and jboss-remoting.jar appear BEFORE jbossall-client.jar.
The working jboss-remoting version is 2.2.3.
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 order) but I have not done anything similar for any conflicts between jboss-messaging-client.jar and jbossall-client.jar. The messaging user guide makes no mention of possible conflicts between these latter two jars and an inspection of them shows no overlapping packages.
I am using jboss-remoting version 2.2.3 (upgraded on the server) and have experimented with both the 2.2.3 and 2.2.3-brew on the client.
Are you using jboss-aop-1.5.6.GA? The messaging guide says to use 2.0.1.GA but this throws errors with AS 4.2.3.
the aop version should be 1.5.6 GA.
I'll examine the user guide and correct it if it is wrong as you said.
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?
I've just come back to this today and upgraded to JBoss Messaging 1.4.5.GA and it all runs with no problem.