[
https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076607#comment-16076607
]
ASF GitHub Bot commented on GEODE-2891:
---------------------------------------
Github user pivotal-jbarrett commented on the issue:
https://github.com/apache/geode-native/pull/106
@gregt5259 This is a solution to the problem but not the solution we as
committers are comfortable committing as it directly conflicts with the correct
change, which is to use type safe durations rather than magic number math and
system wide properties to create a confusing array of time values.
If you want this change sooner than later you could implement it using
std::chrono::duration as outlined in GEODE-3137 or maintain a fork with your
change in it.
> 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
> 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)
