[
https://issues.apache.org/jira/browse/GEODE-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols closed GEODE-6164.
-------------------------------
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> 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)
