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

Memory Leak: RemoteConnectionHandler objects are created but not being freed when jboss-cli commands are executed

    XMLWordPrintable

Details

    • Hide

      1. Install and start Wildfly 17.0.1.Final Java EE Full & Web Distribution
      2. Execute a random command using jboss-cli.
      Examples:
      jboss-cli.sh -c --commands="ls"
      jboss-cli.sh -c --commands="version"

      3. using jcmd, search for the occurrences of "RemoteConnectionHandler" on the class-histogram:
      jcmd <PID> GC.class_histogram | grep RemoteConnectionHandler

      4. Repeat steps 2 and 3 and observe the ever increasing number of RemoteConnectionHandler objects

      Show
      1. Install and start Wildfly 17.0.1.Final Java EE Full & Web Distribution 2. Execute a random command using jboss-cli. Examples: jboss-cli.sh -c --commands="ls" jboss-cli.sh -c --commands="version" 3. using jcmd, search for the occurrences of "RemoteConnectionHandler" on the class-histogram: jcmd <PID> GC.class_histogram | grep RemoteConnectionHandler 4. Repeat steps 2 and 3 and observe the ever increasing number of RemoteConnectionHandler objects

    Description

      When the user executes jboss-cli commands on a fresh installation of wildfly, RemoteConnectionHandler objects are created but never released.

      We identified this problem when we configured a readiness probe on openshift using jboss-cli (repeating every 15 seconds) and the memory started to increase along the days. The application was in development and nobody was accessing it, but the memory increased nonetheless.

      Attachments

        Issue Links

          Activity

            People

              flaviarnn Flavia Rainone
              super6349 super 6349 (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: