1 Reply Latest reply on Feb 21, 2012 9:46 AM by dmlloyd

    Exception: signer information does not match signer information of other classes in the same package

    amalrajvinoth

      Hi,

       

      The following exception is thrown when I try with JBoss AS 5.1.0 with Infinispan 5.0.1Final,

       

      Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: org.jboss.logging.BasicLogger, msg=class "org.jboss.logging.BasicLogger"'s signer information does not match signer information of other classes in the same package

          at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:181)

          at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:276)

          at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1138)

          at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:862)

          at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:502)

          at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:447)

          at java.lang.ClassLoader.loadClass(ClassLoader.java:248)

          ... 95 more

      Caused by: java.lang.SecurityException: class "org.jboss.logging.BasicLogger"'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)

          at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:135)

          at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)

          at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:455)

          at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:267)

          at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:166)

          ... 101 more

       

      I checked the jboss-logging.jar which is the only jar has "org.jboss.logging.BasicLogger" class in my classpath.

      I have no idea regarding the exception. this is working fine with standalone JVM.

       

      Please help me to solve the issue.

       

      thanks in advance. amal raj.

        • 1. Re: Exception: signer information does not match signer information of other classes in the same package
          dmlloyd

          If you want to use a library (like Infinispan) which uses the more recent JBoss Logging 3.x, and you have signed packages, you have to remove all vestiges of JBoss Logging 2.x which include jboss-logging-spi.jar, jboss-logging-log4j.jar, and jboss-logging-jul.jar.  But be aware that you may run into other problems, especially if your logging configuration references classes which were present in JBoss Logging 2.x.  Using JBoss Logging 3.x is not exactly supported on JBoss AS 5.x but you can give it a shot.