[
https://issues.apache.org/jira/browse/GEODE-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758796#comment-16758796
]
ASF subversion and git services commented on GEODE-6344:
--------------------------------------------------------
Commit 7d4b74cc0aebaaf815b0a265439f1fa7b98bf99b in geode's branch
refs/heads/feature/GEODE-6291 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7d4b74c ]
GEODE-6344: should revert GEODE-1183 before a better fix
GEODE-6344: fix CacheClientNotifierDUnitTest to remove the 2nd cacheserver
> should revert GEODE-1183 before a better fix
> --------------------------------------------
>
> Key: GEODE-6344
> URL: https://issues.apache.org/jira/browse/GEODE-6344
> Project: Geode
> Issue Type: Bug
> Reporter: xiaojian zhou
> Assignee: xiaojian zhou
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> GEODE-1183 was introduced for a scenario that there're 2 cache-servers at the
> same jvm, the client will try to create 2 proxy to the server, but since it's
> the same proxy id, it would end up close/recreate forever.
> GEODE-1183 will reject an incoming create-proxy request if the server found
> there's an existing proxy with the same id and its socket is still connected.
> However, this fix caused some side effects. For example, if the client read
> time out, it requested the server to recreate the proxy, the server will
> reject this request and the client will never reconnect.
> This is due to that at the server side, it cannot determine it's a reconnect
> request or the same client requests to connect to the 2nd cache-server on the
> same jvm.
> There's a proposal to introduce a parameter at the client to fix it. However,
> before this new re-fix, we decided to revert the original GEODE-1183 to avoid
> its side-effect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
