[
https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072612#comment-16072612
]
ASF GitHub Bot commented on GEODE-2891:
---------------------------------------
Github user pivotal-jbarrett commented on the issue:
https://github.com/apache/geode-native/pull/105
> I suggest to fix the issue by defining handshake pseudo message within
the range probably defined for such pseudo messages by original design i.e.:
> typedef enum {
> /* Server couldn't read message; handle it like a server side
> exception that needs retries */
> HANDSHAKE = -3
> NOT_PUBLIC_API_WITH_TIMEOUT = -2,
I think that would certainly work better but I think ultimately the fix is
to remove the ambiguity between the C++ API and the Server API by strongly
typing the duration values as addressed in the mentioned tickets. All duration
values can be cast to the internal API supported unit without any ambiguity.
After which there is no need to create this pseudo message to change the unit
of the ambiguous int value.
> 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
> 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)
