[jboss-jira] [JBoss JIRA] (WFLY-951) It is not possible to enable AtomicActionExpiryScanner in EAP 6.x

[Tom Jenkinson (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958426#comment-12958426 ] 

Tom Jenkinson commented on WFLY-951:
------------------------------------

I think we should expose this via the subsystem configuration. [~maeste], are you OK to take a look at it for us please?
                
> 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
>
> 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 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