EAP5 client signed libraries cannot be loaded as custom module in EAP 6.3
Issue
- We are getting below WARN while using EAP 5 client signed libraries with EAP 6. Is there any issue/bug with this :
08:39:06,930 WARN [org.jboss.modules] (ServerService Thread Pool -- 63) Failed to define class org.jnp.interfaces.NamingContextFactory in Module "eap5-client:main" from local module loader @5fd0f0db (finder: local module finder @e74eb02 (roots: /usr/local/EAP-6.3.0/jboss-eap-6.3/modules,/usr/local/EAP-6.3.0/jboss-eap-6.3/modules/system/layers/base/.overlays/layer-base-jboss-eap-6.3.1.CP,/usr/local/EAP-6.3.0/jboss-eap-6.3/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
at java.lang.ClassLoader.checkCerts(ClassLoader.java:952) [rt.jar:1.7.0_67]
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:666) [rt.jar:1.7.0_67]
at java.lang.ClassLoader.defineClass(ClassLoader.java:794) [rt.jar:1.7.0_67]
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.4.Final-redhat-1]
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.4.Final-redhat-1]
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.4.Final-redhat-1]
Environment
- RedHat JBoss Enterprise Application Platform(EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
