[IGNITE-2766] Cache instance is closed when client disconnects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0.final
• Fix Version/s: 2.5
• Component/s: cache
• Assignee: Ilya Kasnacheev
• Reporter: Valentin Kulichenko
• Created: 04/Mar/16 22:34
• Updated: 28/May/20 12:53
• Resolved: 13/Apr/18 21:50

Description

In case client disconnects and reconnects after network timeout (i.e., with a new ID), all cache instances acquired by this client are closed and are not functional. User has to create a special logic to handle this case.

Cache proxy should be able to handle this automatically.

Issue Links

• causes: IGNITE-13088 Improve exception when cache not exists after client restart
• is related to: IGNITE-8978 Affinity throws "IgniteException: Failed to find cache" after an Ignite client re-connect
• is related to: IGNITE-8301 testReconnectCacheDestroyedAndCreated should excpect recreated client cache
• is related to: IGNITE-2765 WebSessionFilter doesn't survive client reconnect
• is related to: IGNITE-2786 SpringCache doesn't survive client reconnect
• is related to: IGNITE-2787 Hibernate L2 cache doesn't survive client reconnect
• relates to: IGNITE-7603 Waiting on reconnect future doesn't help when client reconnects after full cluster restart
• links to: GitHub Pull Request #2816
• links to: GitHub Pull Request #2870
• links to: GitHub Pull Request #3077
• links to: GitHub Pull Request #3417
• links to: GitHub Pull Request #3853