[ https://issues.apache.org/jira/browse/GEODE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547206#comment-16547206 ]
ASF subversion and git services commented on GEODE-5376: -------------------------------------------------------- Commit 69d51c91a13ebc89d31ded924690c2a5e3c369e7 in geode's branch refs/heads/feature/GEODE-5376 from eshu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=69d51c9 ] GEODE-5376: Move SynchronizationRunnable to TXState Different threads can handle JTA beforeCompletion and afterCompletion after client failover. Use TXStateSynchronizationRunnable to handle this case. > 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: 0.5h > 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)