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

    • Bug
    • Resolution: Done
    • Blocker
    • 18.0.0.Final
    • 16.0.0.Final, 17.0.0.Final, 17.0.1.Final
    • CLI, Remoting, Web (Undertow)
    • None
    • 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

          is incorporated by

          Bug - A problem which impairs or prevents the functions of the product. REM3-347 CloseListener of http connections not being invoked when connection is upgraded to remoting

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Component Upgrade - A task tracking an update to a bundled component WFCORE-4658 Upgrade jboss-remoting to 5.0.15.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component WFLY-12562 Upgrade WildFly Core 10.0.0.Beta9

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFLY

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved: