[ https://issues.jboss.org/browse/AS7-6272?page=com.atlassian.jira.plugin.s... ] Tom Ross updated AS7-6272: -------------------------- Description: It should be possible to add AtomicActionExpiryScanner to the EAP 6 configuration as outline below: {noformat} <system-properties> <property name="RecoveryEnvironmentBean.expiryScannerClassNames" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner\\s+com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/> </system-properties> {noformat}  Unfortunately the value of the RecoveryEnvironmentBean.expiryScannerClassNames seems to be overwritten in the ArjunaRecoveryManagerService class. As a result there is no way easy way of removing transaction manager debris from object store. was: It should be possible to add AtomicActionExpiryScanner to the EAP 6 configuration as outline below: {noformat} <system-properties> <property name="RecoveryEnvironmentBean.expiryScannerClassNames" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner\\s+com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/> </system-properties> {noformat}  Unfortunately it seems that the value of the RecoveryEnvironmentBean.expiryScannerClassNames seems to be overwritten in the ArjunaRecoveryManagerService class. As a result there is no way easy way of removing transaction manager debris from object store. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira