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

XTS transactions - failing on deployment - jar signing problem

    XMLWordPrintable

Details

    • Not Required
    • NEW

    Description

      XTS transaction deployment failing with error:

      DEPLOYMENTS IN ERROR:
  Deployment "XTSService" is in error due to the following reason(s): java.lang.SecurityException: class "org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryModule"'s signer information does not match signer information of other classes in the same package

      Currently it's not possible to use XTS transaction on ER4.

      The reason (what I can say) is that the XTS transactions are distributed as sar module which is unpacked to deploy dir for installation (check $JBOSS_HOME/docs/examples/transactions/README.txt). The .sar contains some jars (which are signed) and exploded directory structure with several classes which are obviously unsigned (as they are exploded).

      The exploded directory structure should be put to jar which will be signed as well.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10428 Unsigned jbossxts.sar in EAP 5.2.0.ER5

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-1342 XTS sar distribution - pack .class files from exploded directory to a jar file

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBTM-2104 XTS war distribution within jbossxts.sar - pack .class files from WEB-INF/classes directory to a jar file

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              anil.saldhana Anil Saldanha (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: