[jira] [Created] (GEODE-3679) Server node should forward client member id to other partition nodes even if it already has a TXState

["Eric Shu (JIRA)" <ji...@apache.org>]

Eric Shu created GEODE-3679:
-------------------------------

             Summary: Server node should forward client member id to other partition nodes even if it already has a TXState
                 Key: GEODE-3679
                 URL: https://issues.apache.org/jira/browse/GEODE-3679
             Project: Geode
          Issue Type: Bug
          Components: transactions
            Reporter: Eric Shu


If the server starts the transaction from client with TXId(clientMember, uniqueId) and bootstrap a TXState as its realDeal, it should still forward the tx originating member to other nodes in a PartitionMessage as long as these msg can not start a new transaction ie FetchKeysMessage. 

Otherwise, the receiving side will construct a transaction with TXId using the server memberId. There could be a case that the server did initiate a real transaction using the same uniqueId. This will cause problem, and other partition node may not process these message as the transaction may be already finished.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)