[jbossts-issues] [JBoss JIRA] Commented: (JBTM-300) Move stale transaction logs
[
https://jira.jboss.org/jira/browse/JBTM-300?page=com.atlassian.jira.plugi...
]
Toshiya Kobayashi commented on JBTM-300:
----------------------------------------
Thank you for backporting.
I put 4.2.3.SP5_CP07-brew jars into EAP 4.3.0 CP06 (SOA-P 4.3.0 CP02) and tested
AtomicActionExpiryScanner.
Then I found that expired tx-logs were copied to "Expired" directory but the
original files were not removed.
find data/tx-object-store
...
data/tx-object-store/HashedActionStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/#197#/7f000001_9020_4b025a1e_2f9
data/tx-object-store/HashedActionStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/Expired/#197#/7f000001_9020_4b025a1e_2f9
...
It's hitting JBTM-418.
Could you take care of JBTM-418 for 4.2.3 branches too?
Move stale transaction logs
---------------------------
Key: JBTM-300
URL: https://jira.jboss.org/jira/browse/JBTM-300
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transaction Core
Reporter: Mark Little
Assignee: Jonathan Halliday
Priority: Optional
Fix For: 4.2.3.SP8, 4.4.0.GA, 4.2.3.CP07
We should generalise the ExpiryScanner implementation of TopLevelTransaction in JTS so
that logs that cannot be recovered after a set period of time are moved elsewhere for
manual intervention.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira