[jira] [Updated] (GEODE-1235) Geode should handle client reconnect scenario and not simply remove disconnected client transaction after 180 seconds

["Anthony Baker (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anthony Baker updated GEODE-1235:
---------------------------------
    Issue Type: Improvement  (was: Bug)

> Geode should handle client reconnect scenario and not simply remove disconnected client transaction after 180 seconds
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-1235
>                 URL: https://issues.apache.org/jira/browse/GEODE-1235
>             Project: Geode
>          Issue Type: Improvement
>          Components: transactions
>            Reporter: Eric Shu
>            Priority: Major
>
> Currently in GEODE, once a client is disconnected from server, all its client transactions are scheduled to be removed in 180 second. It is possible that the client reconnects to another server, and the transactions could continue. If a transaction is not finished (committed or rolled back) in 180 seconds, the scheduled transaction removal will kick in and cause the existing transactional operations to be lost and client won't know about this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)