Michael Musgrove created JBTM-1137: -------------------------------------- Summary: ArjunaJTS recovery quickstart sometimes throws CORBA.OBJECT_NOT_EXIST exception Key: JBTM-1137 URL: https://issues.jboss.org/browse/JBTM-1137 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 5.0.0.M1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 6.0.0.Final Running the JTS recovery quickstart (ArjunaJTS/recovery) sometimes, but not always, throws an org.omg.CORBA.OBJECT_NOT_EXIST exception during recovery. When it does happen the relevant XA resoruces still complete but the corresponding log record is left in the ObjectStore and then moved to AssumedComplete on the next pass. When it does happen I notice that there are two threads replaying phase 2, the one that completes removes the servants (for the XA resources) from the ORBs active object map so that when the other thread replays phase 2 the CORBA object no longer exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira