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

Network connection leak

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.1.0.Final
    • Fix Version/s: 9.0.0.Alpha1
    • Component/s: Web (Undertow)
    • Labels:
      None
    • Environment:

      Linux 2.6.38-16-server
      Java(TM) SE Runtime Environment (build 1.7.0_45-b18)

      Description

      When using Asynchronous servlets and AsyncListeners for long polling we observe a connection leak in the undertow subsystem.

      Heap dumps show a large number of org.xnio.io.NioSocketConduit, io.undertow.server.protocol.http.HttpServerConnection and related objects.

      However, since the effective number of connections is far less, nearly all AsyncContext instances we find are in a complete state and lsof output returns a large number of sockets with 'can't identify protocol' entries indicating that sockets are kept open by the JVM but are in fact half closed by the network stack.

      Not all connections appear to be leaking, but over time, depending on the load, the server instance fills up.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                swd847 Stuart Douglas
                Reporter:
                jan.vanhercke Jan Vanhercke
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: