[ https://issues.apache.org/jira/browse/GEODE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Shu reassigned GEODE-5376: ------------------------------- Assignee: Eric Shu > In JTA, Geode afterCompletion may fail even though the JTA host still > available > ------------------------------------------------------------------------------- > > Key: GEODE-5376 > URL: https://issues.apache.org/jira/browse/GEODE-5376 > Project: Geode > Issue Type: Bug > Components: transactions > Reporter: Eric Shu > Assignee: Eric Shu > Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > When JTA is hosted on a server S2, and there is another server S1 handles the > client JTA request. After the S1 executed JTA beforeCompletion initiated from > client, the S2's P2P reader thread for S1 will hold the locks for the JTA. If > at the time, S1 is lost/shut down, client will failover to another server to > try afterCompletion. The afterCompletion attempt will fail as the new thread > does not hold the lock. This will cause the client JTA to fail due to > CommitConflict, even though there is not concurrent commit operations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)