[jbossts-issues] [JBoss JIRA] (JBTM-1943) Allow the safety interval for RecoveryXids to be configurable

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JBTM-1943:
-----------------------------------------------

tom.jenkinson at redhat.com made a comment on [bug 1009981|https://bugzilla.redhat.com/show_bug.cgi?id=1009981]

I created an enhancement request over on Jira for you for the JBTM part. There would need to be a WFLY issue to expose the new config via the AS for it to be formally accepted as supportable (and QE would need to test it)
                
> Allow the safety interval for RecoveryXids to be configurable
> -------------------------------------------------------------
>
>                 Key: JBTM-1943
>                 URL: https://issues.jboss.org/browse/JBTM-1943
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: JTA
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>             Fix For: 4.17.11, 5.0.0.M5
>
>
> Currently it is hard coded to 10 seconds. It is possible that under load this could be possible to breach. Allow the setting to be configurable.
> Breaching the threshold does not pose data integrity issues as the scenario where it becomes an issue is when the transaction has completed during a recovery scan. It will result in calling rollback(xid1) on the RM but as that RM is guaranteed to have had commit(xid1) (or rollback) on it already during transaction completion the only impact is an unsightly stack trace.

--
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