[jboss-jira] [JBoss JIRA] (WFLY-3536) Wildfly 8.1.0 Final keeps established connections forever
[
https://issues.jboss.org/browse/WFLY-3536?page=com.atlassian.jira.plugin....
]
Seth Miller commented on WFLY-3536:
-----------------------------------
Our solution was to update to the 8.2 builds (building our own RPM) so that we can take
advantage of the read-timeout as part of the undertow 1.2 schema in standalone.xml, eg:
{code}
<subsystem xmlns="urn:jboss:domain:undertow:1.2">
<server name="default-server"
servlet-container="default">
<http-listener name="default" socket-binding="http"
buffer-pool="default" tcp-keep-alive="true"
read-timeout="60000"/>
...
{code}
Note the undertow schema version (1.2) and the read-timeout setting of 1 minute. This was
the default in the version of Tomcat that shipped with Wildfly 7.x. I would like to see
this read-timeout value set as the default going forward in Undertow, actually.
I am not aware of a workaround on 8.1; I even tried setting the tcp_keepalive_time at the
OS layer.
Wildfly 8.1.0 Final keeps established connections forever
---------------------------------------------------------
Key: WFLY-3536
URL: https://issues.jboss.org/browse/WFLY-3536
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.1.0.Final
Environment: Ubuntu on Azure VM using Java-7 or Java-8.
Reporter: Renan Polo Montebelo
Assignee: Stuart Douglas
Wildfly 8.1.0 Final seams to keep established TCP connections forever, instead of closing
it after the time configured in the IO worker (default 60s). I only noticed this from
clients using an Android app, so I guess that their Android App is not behaving well, but
Wildfly should be able to handle such situation nicely.
If I activate "tcp-keep-alive" in
/subsystem=undertow/server=default-server/http-listener=default the situation gets a lot
better, although it is still not ideal.
After some 48 hours my Wildfly freezes because there are more than 4K tcp connections
established. Seams that only WEB module freezes, because scheduled timers still work (I
can see activity in my log). I've checked for TCP connections using netstat -n.
JBoss Web Server in 7.1.x confirmed not to have this issue. My deployed application is
basically JPA / EJB / JAX-RS (Resteasy)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)