I have seen something like this before when different versions of JBoss remoting are used on the server and client side.
Can you check you have
a) Dropped remoting 2.2.2-SP1 in the server/lib directory on your as profile.
b) Make sure remoting 2.2.2-SP1 is the first entry on the client classpath as per install instructions.
You were somewhat right :)
As I said before I was using JBR 222SP1 but not 222SP1-brew. With the latter one everything works. Whats the difference between the two ?
They should be the same.
-brew just means the jar is rebuilt from source in a controlled redhat build environment - slightly worrying they are different! are you sure?
Library I was using before (which didn't work with JBM140SP1)
Library which I use now and it works well with JBM140SP1:
I'll ask the remoting team to investigate.
The only *expected* difference between 2.2.2.SP1 and 2.2.2.SP1-brew is that the former was built with jdk 1.4 and the latter with jdk 1.5. The difference shouldn't cause the messages you saw, which, as Tim points out, suggests a significant version difference.
As an experiment, I ran the queue example from JBossMessaging 1.4.0.GA against JBossAS 4.2.0.GA using 2.2.2.SP1 the first time and 2.2.2.SP1-brew the second time. Both runs passed.
Which leaves me stumped. Are you sure that you didn't have another version of Remoting on the classpath somewhere? Don't forget, the Remoting classes are also in /client/jbossall-client.jar.