[jboss-jira] [JBoss JIRA] (WFLY-3536) Wildfly 8.1.0 Final keeps established connections forever

[Renan Polo Montebelo (JIRA)]

Renan Polo Montebelo created WFLY-3536:
------------------------------------------

             Summary: 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
      Security Level: Public (Everyone can see)
          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.2.6#6264)