Tom Ross created AS7-6272: ----------------------------- Summary: It is not possible to enable AtomicActionExpiryScanner in EAP 6.x Key: AS7-6272 URL: https://issues.jboss.org/browse/AS7-6272 Project: Application Server 7 Issue Type: Bug Components: ConfigAdmin Affects Versions: 7.1.3.Final (EAP) Environment: JBoss EAP 6.01 Reporter: Tom Ross Assignee: David Bosschaert 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 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