[jira] [Resolved] (GEODE-3409) Protobuf Client Can't Connect Once Connection Limit Has Been Reached, Even After Connections Closed

["Bruce Schuchardt (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Schuchardt resolved GEODE-3409.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

> Protobuf Client Can't Connect Once Connection Limit Has Been Reached, Even After Connections Closed
> ---------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-3409
>                 URL: https://issues.apache.org/jira/browse/GEODE-3409
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Michael Martell
>             Fix For: 1.3.0
>
>         Attachments: Program.cs, sockclient.java
>
>
> We have a C# sample application (see attached) that connects to geode used the new binary protocol. It floods the server continually with socket connections and quickly reaches the default maximum connections of 800. When the client app closes, all 800 connections appear to be closed by the server (indeed 800 "Closed connection" messages appear in the server log). Running the application again, the server immediately rejects even the first connection request.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)