Based on the previous thread that you mentioned, I'm afraid that the CompressingMarshaller/UnMarshaller must be broken, and I haven't had the opportunity to find out why.
The socket transport prefixes each request and response with a version byte, and if you see a message complaining about an incorrect version, it probably means that that the CompressingUnMarshaller is returning in incorrect byte.
If you can figure out why the CompressingMarshaller/UnMarshaller isn't working, that would be great.
Thanks for the reply. My environment is, an external tomcat web app making EJB3 calls to JBoss server.
With my limited knowledge, I have a couple of guesses. Tomcat by nature has multi user environment. That means multiple coversations happen at the same time. I think remoting tries to reuse open connections. Could there be an issue with multiple conversations serialized into the same socket connection and this causes an unsynchronized status between the client and server socket that is only exposed when compression (or may be any other hooks) attached on both ends?
One more thing to add...
I also see not in GZIP format on the server side...