Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3536

Wildfly 8.1.0 Final keeps established connections forever

    XMLWordPrintable

Details

    • Hide

      Deploy a JAX-RS application, use telnet to make a connection and HTTP GET an url. Do not close connection gracefully and wait... after some time, TCP connection should be dropped but can be verified in netstat -n

      Show
      Deploy a JAX-RS application, use telnet to make a connection and HTTP GET an url. Do not close connection gracefully and wait... after some time, TCP connection should be dropped but can be verified in netstat -n
    • Compatibility/Configuration, User Experience

    Description

      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)

      Attachments

        Activity

          People

            sdouglas1@redhat.com Stuart Douglas
            renan.polo.montebelo Renan Polo Montebelo (Inactive)
            Votes:
            8 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: