[
https://issues.jboss.org/browse/ISPN-1080?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-1080:
--------------------------------
Description:
Reading the JBossTS recovery documentation[1], the recovery process should be able to pull
recovery info from ISPN's XAResource implementation by calling .recover(). The issue
is that this method needs to be called in the same process where ISPN node leaves and ATM
its not possible to invoke it from a different process.
This documentation would also be useful for users that want to set up/play with
transaction recovery in general.
[1]
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4...
was:
Reading the JBossTS recovery documentation[1], the recovery process should be able to pull
recovery info from ISPN's XAResource implementation by calling .recover(). The issue
is that this method needs to be called in the same process where ISPN node leaves and ATM
its not possible to invoke it from a different process.
This would also be useful for users that want to set up/play with transaction recovery in
general.
[1]
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4...
Investigate and document XA recovery integration with JBossTS
-------------------------------------------------------------
Key: ISPN-1080
URL:
https://issues.jboss.org/browse/ISPN-1080
Project: Infinispan
Issue Type: Feature Request
Reporter: Mircea Markus
Assignee: Mircea Markus
Labels: jta, recovery, xa
Fix For: 5.0.0.FINAL
Reading the JBossTS recovery documentation[1], the recovery process should be able to
pull recovery info from ISPN's XAResource implementation by calling .recover(). The
issue is that this method needs to be called in the same process where ISPN node leaves
and ATM its not possible to invoke it from a different process.
This documentation would also be useful for users that want to set up/play with
transaction recovery in general.
[1]
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4...
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira