xiaojian zhou created GEODE-6164:
------------------------------------
Summary: CacheClientProxy's closeSocket() should be called
atomically
Key: GEODE-6164
URL: https://issues.apache.org/jira/browse/GEODE-6164
Project: Geode
Issue Type: Bug
Components: client/server
Reporter: xiaojian zhou
When multiple threads are calling CacheClientProxy.close() together. One thread
is working on this._socketClosed.compareAndSet, another thread may skip this
step and set this._remoteHostAddress to null. This will end up with NPE in
this._cacheClientNotifier.getSocketCloser().asyncClose(this._socket,
this._remoteHostAddress, null);
To fix it, we will force closeSocket() to be called atomically and only that
thread can set "this._remoteHostAddress = null;"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
