Hi, How one can be assigned to this issue to solve it ? Actually who is going to switch it from backlog forward?
Regards, Dor -----Original Message----- From: Gregory Vortman (JIRA) [mailto:j...@apache.org] Sent: יום ב 08 מאי 2017 14:09 To: dev@geode.apache.org Subject: [jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client [ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Vortman updated GEODE-2891: ----------------------------------- Attachment: gemfire-connect-timeout-violation.docx > 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) 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>
