Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-7820

Transaction manager runtime configuration is not enriched with system properties from standalone xml

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.DR10
    • 7.1.0.DR9
    • Transactions
    • None
    • Hide

      Could be reproduced with crashrec testsuite where system property RecoveryEnvironmentBean.expiryScannerClassNames is defined as application container system property.

      git clone http://git.app.eng.bos.redhat.com/git/jbossqe-eap-tests-transactions.git
export JBOSS_HOME=... (downloadable at http://download.eng.brq.redhat.com/devel/candidates/JBEAP/)
mvn clean verify -am -pl jbossts -DfailIfNoTests=false -fn -Djbossts.noJTS -Dtest=JPAProxyCrashRecoveryTestCase#testAAExpiryScanner
      Show
      Could be reproduced with crashrec testsuite where system property RecoveryEnvironmentBean.expiryScannerClassNames is defined as application container system property. git clone http: //git.app.eng.bos.redhat.com/git/jbossqe-eap-tests-transactions.git export JBOSS_HOME=... (downloadable at http: //download.eng.brq.redhat.com/devel/candidates/JBEAP/) mvn clean verify -am -pl jbossts -DfailIfNoTests= false -fn -Djbossts.noJTS -Dtest=JPAProxyCrashRecoveryTestCase#testAAExpiryScanner

    Description

      I can see trouble and regression against behavior of 7.0.0.GA (and other prior 7.1.0 DR versions) where configuration of transaction manager which is defined inside of setting MBeans is not enriched from system properties which are defined as part of standalone .xm file.

      When system property is set in standalone xml file as

      <system-properties>
  <property name="RecoveryEnvironmentBean.expiryScannerClassNames" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/>
</system-properties>

      then it's not propagated to RecoveryEnvironmentBean when container is started.

      I could see that method loading system properties at AbstractPropertiesFactory (https://github.com/jbosstm/narayana/blob/master/common/classes/com/arjuna/common/util/propertyservice/AbstractPropertiesFactory.java#L119) does not provide those which are part of the container config. That worked with DR8 fine. I didn't go deeper if this is really issue of TM/integration or some change in container.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7785 Transaction manager runtime configuration is not enriched with system properties from standalone xml

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              thjenkin@redhat.com Tom Jenkinson
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: