Because of the way the as7.1 mbean connector loads the client jar direct from the server installation, the auto-connection to jmx does not benefit from the remoting upgrade committed by JBIDE-11871. The client jar for a 7.1.0 installation, for example, will still use remoting 3.2.2 rather than the astools-bundled 3.2.7.

Possible solutions are prevent auto-connection of jmx or somehow force the 3.2.7 remoting jar onto the classpath before the as7.1.0 client jar to ensure 3.2.7 classes take precedence.