Jboss 5 instrumentation with SteelCentral AppInternals 10.x fails with signer information mismatch

We are trying to instrument Jboss 5, EAP 5 with SteelCentral AppInternals 10.x and the application server fails. We do see the below error in the application log.

WARN  [ClassLoaderManager] Unexpected error during load of:org.jboss.aop.asintegration.jboss5.AOPClassLoaderScopingPolicyWithRegistry
java.lang.SecurityException: class "org.jboss.aop.asintegration.jboss5.AOPClassLoaderScopingPolicyWithRegistry"'s signer information does not match signer information of other classes in the same package
    at java.lang.ClassLoader.checkCerts(ClassLoader.java:807)
    at java.lang.ClassLoader.preDefineClass(ClassLoader.java:488)
    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:626)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
    at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:67)
    at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:633)
    at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:592)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:591)
    at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:568)

How do we resolve this and instrument the application?

This is a known issue and the cause of the issue is presence of signed jar files in Jboss 5.
Jboss engineering team have mentioned that they abandoned signing of Jboss jar files for EAP 6. The suggestion they had for customer's is to remove the signature from the Jboss jar files.

Riverbed did open a bug report to track the issue internally and there do not seem to be an proper workaround for the issue. We do encourage customer's to remove signatures from their jar files as Jboss team have suggested. In case customers are unable to remove the signatures as mentioned there is a possible workaround to try.

Workaround:

In the AppInternals configuration under which the Jboss JVM is listed please add the below parameter in the configuration overrides section and save the changes. Restart the application server.

{"internal.load.class.as.resource":false}



**please open a technical support case if you still have any issues
 

Jboss, SteelCentral AppInternals