[
https://issues.apache.org/jira/browse/GEODE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-3409:
------------------------------------
Attachment: sockclient.java
here's a java client that reproduces the issue. The server log has many
entries like this:
[warning 2017/08/22 08:39:24.008 PDT server1 <Handshaker 0.0.0.0/0.0.0.0:15963
Thread 2> tid=0x4e] Rejected connection from /127.0.0.1 because current
connection count of 800 is greater than or equal to the configured max of 800
> 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
> 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)
