You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Gregory Vortman (JIRA)" <ji...@apache.org> on 2017/10/12 07:30:00 UTC
[jira] [Commented] (GEODE-2891) connect-timeout violation in C++
Native Client
[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201560#comment-16201560 ]
Gregory Vortman commented on GEODE-2891:
----------------------------------------
I don't have email access until 17.10.2017
My private email account is: gregory.vortman@gmail.com
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
> connect-timeout violation in C++ Native Client
> ----------------------------------------------
>
> Key: GEODE-2891
> URL: https://issues.apache.org/jira/browse/GEODE-2891
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Gregory Vortman
> Assignee: Jacob S. Barrett
> Fix For: 1.3.0
>
> Attachments: GEODE-connect-timeout-violation.docx
>
>
> 1. C++ native client doesn’t honour read-timeout-milli-sec in a consistent way while connecting to a server
> 2. The lock on the connection pool has a very high granularity. Even if the client can’t connect to one server, all other threads which are working with totally different servers get affected by it
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)