[
https://issues.jboss.org/browse/JBTM-1644?page=com.atlassian.jira.plugin....
]
Michael Musgrove updated JBTM-1644:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Documentation has been added to the failure recovery guide.
The previous comment indicated how to test the behavior by modifying an existing
quickstart. However, it may still be useful to have a dedicated quickstart which explains
what is happening "under the covers" as the various stages of recovery progress.
If there is call for such a quickstart then the JIRA should be re-opened.
Thoroughly document how to recover a local JTA object store from a
different node (perhaps with quickstart?)
------------------------------------------------------------------------------------------------------------
Key: JBTM-1644
URL:
https://issues.jboss.org/browse/JBTM-1644
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Demonstrator, Documentation
Reporter: Tom Jenkinson
Assignee: Michael Musgrove
Priority: Critical
Fix For: 5.0.0.M3
Attachments: use-postgresql.patch
Please can you document any restrictions (stating none if there are none). How to
configure the recovery manager (e.g. specific node id, not *). Considerations a user
should have (not to connect more than one recovery manager to the same store at once,
suggestions for how to restrict that - maybe object store specific?)
Object store specific information, e.g. if you are using filesystem/hornetq/jdbc do any
of them ensure that only one process is accessing at the same time?
A simple quickstart demonstrating how to use (maybe JDBC object store inside AS7 would be
most appropriate) would be useful.
Does IP address play a role, are there any other restrictions?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira