RMIAdaptor hashs not compatible between 3.2.8 & 4.0.x

The jboss-4.0-compatibility-matrix tests 3.2.x clients against a 4.0.x server. These tests are currently failing.

http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-compatibility-matrix

Clebert did some debugging and determined this is failing due to changes in the org.jboss.jmx.adaptor.rmi.RMIAdaptor interface between 3.2.x and 4.0.x.

Here is the error:

Failed to find method for hash:-1844321052135939888 available={3851446659803776630=public abstract void javax.management.MBeanServerConnection.removeNotificationListener(javax.management.ObjectName,javax.management.NotificationListener,javax.management.NotificationFilter,java.lang.Object) throws javax.management.InstanceNotFoundException ...
at org.jboss.invocation.MarshalledInvocation.getMethod(MarshalledInvocation.java:407)
at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:234)
...

This test uses the org.jboss.j2ee.Serialization flag on the client. No serialization flags are passed to the server:

<test-compatibility client-version="3_2_x" serialization-flag="-Dnone" client-serialization-flag="-Dorg.jboss.j2ee.Serialization"/>

Here is the diff between RMIAdaptor on 3.2 vs 4.0:

http://anoncvs.forge.jboss.com/viewrep/JBoss/jboss/src/main/org/jboss/jmx/adaptor/rmi/RMIAdaptor.java?r1=1.2.2.3&r2=1.6.6.1