[jbossts-issues] [JBoss JIRA] (JBTM-847) Look into how AssumedComplete works for ArjunaJTA (and jtax)

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Fri Oct 26 08:20:02 EDT 2012

     [ https://issues.jboss.org/browse/JBTM-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson closed JBTM-847.

    Resolution: Done

> Look into how AssumedComplete works for ArjunaJTA (and jtax)
> ------------------------------------------------------------
>                 Key: JBTM-847
>                 URL: https://issues.jboss.org/browse/JBTM-847
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JTA
>    Affects Versions: 4.15.1
>            Reporter: Mark Little
>            Assignee: Mark Little
>             Fix For: 5.0.0.M1, 4.15.1
> When a transaction cannot be completed over a long period of time, a scanner is supposed to kick in and move the log elsewhere. Those scanners exist in ArjunaCore and ArjunaJTS, but do not appear to be there in ArjunaJTA. It should be straightforward to add them by using the base class in ArjunaCore, but investigate whether they are present already and just not obvious.

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

More information about the jbossts-issues mailing list