[jbossts-issues] [JBoss JIRA] Commented: (JBTM-847) Look into how AssumedComplete works for ArjunaJTA (and jtax)
[
https://issues.jboss.org/browse/JBTM-847?page=com.atlassian.jira.plugin.s...
]
Mark Little commented on JBTM-847:
----------------------------------
For local JTA, the basic TransactionImple wraps AtomicAction, so for that the standard
AtomicActionExpiryScanner will work. SubordinateAtomicAction (used by JCA) does likewise.
For the JTS version of JTA, the basic AtomicTransaction is an extension of the JTS
AtomicTransaction, which wraps the JTS transaction implementation. This means that the
ExpiredAssumedCompleteScanner and friends will work. The SubordinateAtomicTransaction
(used by JCA) does likewise.
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira