[ http://jira.jboss.com/jira/browse/JBTM-346?page=all ] Andrew Dinn closed JBTM-346. ---------------------------- Resolution: Done 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBTM-346?page=all ] Andrew Dinn closed JBTM-346. ---------------------------- Resolution: Done Fixed by revision 19625 Modified Inventory classes to enable removal of inventory items as well as deletion. XTSService now gets ACCoordinatorRecoveryModule to install() its ParticipantRecordSetup item in the inventory when the module is added to the RecoveryManager module list and uninstall() it when the module is removed. Implementing the latter operation required adding a waitForSync flag to the RecoveryManager remove() operation. This ensures that any in-progress scan which might be using the inventory entry is completed before the inventory remove operations is attempted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBTM-346?page=all ] Jonathan Halliday updated JBTM-346: ----------------------------------- Fix Version/s: 4.4.CR2 (was: 4.4.CR1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira