Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-2971

Applications that use Hibernate with cglib proxies fail to deploy due to java.lang.SecurityException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • EAP_EWP 5.1.0
    • EAP 5.0.0.CR5, EAP 5.0.0, EAP 5.0.1.CR1
    • Hibernate
    • None
    • Release Notes
    • Workaround Exists
    • Hide

      A workaround is to replace:
      jboss-eap-5.0/jboss-as/common/lib/cglib.jar
      with an "unsigned" version of cglib.jar, which can be downloaded from:
      http://repository.jboss.com/maven2-brew/cglib/cglib/2.2/cglib-2.2.jar

      Show
      A workaround is to replace: jboss-eap-5.0/jboss-as/common/lib/cglib.jar with an "unsigned" version of cglib.jar, which can be downloaded from: http://repository.jboss.com/maven2-brew/cglib/cglib/2.2/cglib-2.2.jar

      Applications that use Hibernate mapped to use cglib as its byte code provider will fail to deploy due to java.lang.SecurityException,

      An example of the error message is:

      Deployment "persistence.unit:unitName=lobtest.ear/lobtest-ejb-1.0-SNAPSHOT.jar#lobtest-jpa-jndi" is in error due to the following reason(s): java.lang.SecurityException: class "com.redhat.gss.lobtest.jpa.Item$$EnhancerByCGLIB$$defd1a7f"'s signer information does not match signer information of other classes in the same package

      This happens because cglib.jar in EAP 5 is signed and the cglib-instrumented proxy uses the same signer information as cglib.jar, instead of the signer information for the applications target class.

              shaozliu Strong Liu(刘少壮) (Inactive)
              gbadner@redhat.com Gail Badner (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: