-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
1.3.4.Final
-
None
-
None
When creating JMS bridge on EAP6, I need to create a custom module with client jars for the external JMS broker (unless it's HornetQ). When I use client jars for JBoss Messaging from EAP 5.2.0 in a module on EAP 6.4.0.DR4 (JBoss Modules 1.3.4.Final), JMS bridge fails to load with "class "org.jboss.aop.advice.AbstractAdvice"'s signer information does not match signer information of other classes in the same package" (details below).
This is not an issue in EAP 6.3.0 (JBoss Modules 1.3.3.Final) and it's not an issue with EAP 6.4.0 and EAP 5.1.2. Only combination of EAP 6.4.0 and EAP 5.2.0 (and also 5.3.0.ER3) shows this error. It's only issue if the jars are signed, everything works as expected if I unsign the client jars.
The errors thrown on EAP6 (I'll add full server log later not to spam the comments):
13:51:06,456 WARN [org.jboss.modules] (ServerService Thread Pool -- 62) Failed to define class org.jnp.interfaces.NamingContextFactory in Module "com.redhat.qa.eap5client.jbm:main" from local module loader @50ee1793 (finder: local module finder @3f4ddd67 (roots: /home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules,/home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules/system/layers/base)): java.lang.SecurityException: class "org.jnp.interfaces.NamingContextFactory"'s signer information does not match signer information of other classes in the same package 13:51:06,470 WARN [org.hornetq.jms.server] (ServerService Thread Pool -- 62) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.jnp.interfaces.NamingContextFactory from classloader ModuleClassLoader for Module "com.redhat.qa.eap5client.jbm:main" from local module loader @50ee1793 (finder: local module finder @3f4ddd67 (roots: /home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules,/home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory from [Module "com.redhat.qa.eap5client.jbm:main" from local module loader @50ee1793 (finder: local module finder @3f4ddd67 (roots: /home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules,/home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules/system/layers/base))]] Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory from [Module "com.redhat.qa.eap5client.jbm:main" from local module loader @50ee1793 (finder: local module finder @3f4ddd67 (roots: /home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules,/home/msvehla/Projects/bugs/signed-modules/repro/jboss-eap-6.4/modules/system/layers/base))]
13:51:11,534 WARN [org.hornetq.jms.server] (pool-4-thread-1) HQ122010: Failed to connect JMS Bridge: java.lang.RuntimeException: Failed to download and/or install client side AOP stack Caused by: java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_596488705: frozen class (cannot edit) Caused by: java.lang.RuntimeException: org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_596488705: frozen class (cannot edit)
