[ http://jira.jboss.com/jira/browse/JBREM-714?page=all ] Ron Sigal closed JBREM-714. --------------------------- Resolution: Done In the socket transport, there are two sources of version incompatibility between Remoting 2.2.0 and older versions. 1. The wire format used by JavaSerializationManager changed in Remoting 2.2.0. Changes in Remoting 2.2.0.SP4 to JavaSerializationManager, SerializableMarshaller, SerializableUnMarshaller, MicroSocketClientInvoker, and ServerThread allow the socket transport to be configured to communicate with older versions. In particular, if the system property "jboss.remoting.pre_2_0_compatible" is set to true or the system property "jboss.remoting.version" is set to 1, then the socket transport from Remoting 2.2.0.SP4 can talk to the socket transport from Remoting 1.x. If the system property "jboss.remoting.version" is set to 2, then the socket transport from Remoting 2.2.0.SP4 can talk to the socket transport from Remoting 2.0.0. 2. In Remoting 1.x, the pooled connection checking facility is turned on by default, and in Remoting 2.x, it is turned off by default. MicroSocketClientInvoker and ServerThread were changed in Remoting 2.2.0.SP4 so that if they are configured with version == 1, they will turn on connection checking by default. There was also an incompatibility in the rmi transport. A change to RemotingRMIClientSocketFactory allows the rmi transport from Remoting 2.2.0.SP4 to talk to the rmi transport from older versions of Remoting. Also, some changes were made to the main build.xml file for the versioning tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira