[
http://jira.jboss.com/jira/browse/JBTM-345?page=comments#action_12403316 ]
Jonathan Halliday commented on JBTM-345:
----------------------------------------
What happens if a module goes away between first and second passes, or during a recovery
pass? Do we need blocking unregister calls for modules so that does not happen?
support dynamic (un)registration of recovery modules
----------------------------------------------------
Key: JBTM-345
URL:
http://jira.jboss.com/jira/browse/JBTM-345
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.3.0.GA
Reporter: Jonathan Halliday
Assigned To: Andrew Dinn
Fix For: 4.4.CR1
XTS will be deployed into JBossAS as a .sar and may be deployed and undeployed over the
lifetime of the AS instance. The recovery code is always resident in JBossAS, it starts as
part of the transaction service. Thus it needs to be able to support XTS registering and
unregistering a recovery module for XTS transactions whilst the system is running.
Right now recovery modules must be in the jbossjt(a|s)-properties.xml file and are read
at startup only. Allow them to be registered and unregistered programatically also. May
need fixes for concurrency control, as the list of registered modules is iterated during
recovery passes and concurrent modifications are a Bad Thing.
--
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