Andrew Dinn closed JBTM-346.
The recovery manager now provides a thread safe mechanism for adding and deleting recovery
modules dynamically and this has been used to add and remove the ACCoordinator recovery
module from the XTS package at XTS service deploy/undeploy.
The changes to the thread model for RecoveryManager/PeriodicRecovery ensure that addition
or removal does not interfere with any concurrent scan. A scanning thread copies the list
(thread-safely) before it commences scanning. However, this implementation does mean that
the list used by a scanning thread to drive recovery may not include changes made to the
list returned by calls to getModuleList(). This might possibly be an issue if the call
were made from the scanner thread by recovery code expecting to find its own recovery
module in the list. At present only XAResourceRecord calls getModuleList() and there is no
issue with it.
XTS coordinator recovery
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: WS-T Implementation, Recovery
Affects Versions: 4.3.0.GA
Reporter: Jonathan Halliday
Assigned To: Andrew Dinn
Fix For: 4.4.CR1
Take the prototype recovery module for XTS coordinator and wire it up to the XTS .sar
deployment, so that it gets registered and unregistered when XTS is deployed/undeployed
into JBossAS. Check that it works.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira