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

[Stefano Maestri (JIRA)]

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

Stefano Maestri commented on WFLY-951:
--------------------------------------

This is a proposal of changes to don't overwrite system property. It will not require any changes in config, and so it would be easier to backport.
https://github.com/maeste/jboss-as/commit/b0a96424211c2107d6b7348c5f610d5a6581631c
Let me know what do you think about it, if you agree I'll send a PR. 
Of course it's possible to move this property into configs, but if I well understood it's quite rare to need it, and so I would prefer to don't ask a schema/DMR update.


> 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 was sent by Atlassian JIRA
(v6.2.6#6264)