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

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

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 9.0.0.Alpha1
    • Component/s: Transactions
    • Labels:
      None
    • Environment:

      JBoss EAP 6.01

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  maeste Stefano Maestri
                  Reporter:
                  raggz Tom Ross
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: