[jboss-jira] [JBoss JIRA] (WFLY-951) It is not possible to enable AtomicActionExpiryScanner in EAP 6.x
[
https://issues.jboss.org/browse/WFLY-951?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on WFLY-951:
----------------------------------------------
Shaun Appleton <sappleto(a)redhat.com> changed the Status of [bug
1086742|https://bugzilla.redhat.com/show_bug.cgi?id=1086742] from NEW to CLOSED
It is not possible to enable AtomicActionExpiryScanner in EAP 6.x
-----------------------------------------------------------------
Key: WFLY-951
URL: https://issues.jboss.org/browse/WFLY-951
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transactions
Environment: JBoss EAP 6.01
Reporter: Tom Ross
Assignee: Stefano Maestri
Fix For: 9.0.0.Beta1
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 easy way
of removing transaction manager debris from object store.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)