Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-951

It is not possible to enable AtomicActionExpiryScanner in EAP 6.x

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.0.Alpha1
    • None
    • Transactions
    • None

    Description

      It should be possible to add AtomicActionExpiryScanner to the EAP 6 configuration as outline below:

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

       
      Unfortunately the value of the RecoveryEnvironmentBean.expiryScannerClassNames seems to be overwritten in the ArjunaRecoveryManagerService class. As a result there is no easy way of removing transaction manager debris from object store.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-12255 WFLY does not accept the Narayana's long version of property expiryScannerClassNames to define expiry scanners

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              smaestri@redhat.com Stefano Maestri
              rhn-support-toross Tom Ross
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: