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

Memory leak in Websocket implementation (8.1.0 Final)

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 8.1.0.Final
    • Fix Version/s: 8.2.0.Final
    • Component/s: Web Sockets
    • Labels:
      None
    • Environment:

      CentOS 7
      Java 1.7.0_65-b17

      Description

      Creating 100k persistent websockets connections, exchanging small strings (with RemoteEndpoint.Basic) and finally disconnecting all connections the memory grows with ~1GB for each 100k. Basically the test is the following: the clients are connecting and sending a hello message to the server; the server is responding with a welcome string and the clients are disconnecting.

      The settings in onOpen() callback are:

      session.setMaxBinaryMessageBufferSize(10240);
      session.setMaxTextMessageBufferSize(10240);
      session.setMaxIdleTimeout(120000);
      session.getUserProperties().put("ts", System.currentTimeMillis());

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                swd847 Stuart Douglas
                Reporter:
                clvclv Veli Cris
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: