[ 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... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1080?page=com.atlassian.jira.plugin.... ] Mircea Markus edited comment on ISPN-1080 at 5/19/11 7:06 AM: -------------------------------------------------------------- TransactionXAAdapter.hashCode depends on the localtransaction associated with the XAResiurce. This is not good, as the TransactionXAAdapter might not be associated to a transaction at all. This is the case when TransactionXAAdapter is used for recovery, and the call results in a NPE. was (Author: mircea.markus): TransactionXAAdapter.hashCode depends on the localtransaction associated with the XAResiurce. This is not good, as the TransactionXAAdapter might not be associated to a transaction at all. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira