Since version 2.0.0, Remoting has preceded each message on the wire with a version byte.
The valid version bytes, currently, are 1, 2, and 22. If you are using the same version
of Remoting on the client and server, there shouldn't be a problem.
But, you said you are using telnet as the client, which, of course, doesn't send a
version byte. If you are using Remoting 2.0.0+, the default behavior is to treat the
first available byte on the stream as a version byte, in this case a 't'.
You want to turn off versioning. If you set the system property
"jboss.remoting.pre_2_0_compatible" to true on the server side, Remoting will
think it is talking to a pre 2.0.0 version of Remoting and will not expect a version
byte.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059502#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...