[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=16009660#comment-16009660 ] Gregory Vortman commented on GEODE-2891: Thanks Jacob. It was my bad. I fixed the attachment and reopening the issue. > 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.3.15#6346)
[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=16007104#comment-16007104 ] Jacob S. Barrett commented on GEODE-2891: - [~gregvo] You need to make sure that issues you report are for the open source project and not for the close source commercial offering. For support on the commercial offering you need to go through support channels. You issue has been marked resolved as Invalid. I you can correct the issue you can re-open 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 > 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)
[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=16003160#comment-16003160 ] Bruce Schuchardt commented on GEODE-2891: - You can work on a clone of the github repo and submit a pull request. You might want to assign the JIRA ticket to someone on your team if you are going to do this. Here is the process for submitting a pull request: https://cwiki.apache.org/confluence/display/GEODE/Code+contributions > 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 > 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)
[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=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)
