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

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

    XMLWordPrintable

Details

    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

          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: