[ https://issues.apache.org/jira/browse/GEODE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darrel Schneider updated GEODE-1235: ------------------------------------ Summary: Geode should handle client reconnect scenario and not simply remove disconnected client transaction after 180 seconds (was: Geode should handle client reconnect scenario and not simply remove disconeected client transaction after 180 seconds) > 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: Bug > Components: transactions > Reporter: Eric Shu > > 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 (v6.3.15#6346)