You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2017/05/09 15:49:04 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=16002921#comment-16002921 ]
Bruce Schuchardt commented on GEODE-2891:
-----------------------------------------
If this is a C++ client issue the component should be "native client", not "client server"
> 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: client/server
> Reporter: Gregory Vortman
> Fix For: 1.1.1
>
> Attachments: gemfire-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.3.15#6346)