Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4801

RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 9.0.1.Final
    • CLI, Management
    • None
    • Hide
      • Configure WildFly in standalone mode
      • Deploy EAR
      • Run JBOSS CLI command to fetch deployment status
      • Collect heap usage histogram of WildFly JVM and note the count of objects of org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler classes
      • Run JBOSS CLI command again, to fetch deployment status
      • Collect histogram again and observe that object count of these classes have increased
      Show
      Configure WildFly in standalone mode Deploy EAR Run JBOSS CLI command to fetch deployment status Collect heap usage histogram of WildFly JVM and note the count of objects of org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler classes Run JBOSS CLI command again, to fetch deployment status Collect histogram again and observe that object count of these classes have increased

    Description

      Heap dump analysis of services deployed in Wildfly standalone deployment show a large number of stale objects of class org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler. These objects are not getting garbage collected and eventually cause JVM to go out of memory.

      Analysis of the heap dump indicate that,

      • All org.jboss.remoting3.ConnectionImpl objects lingering around are CLOSED as the state and associated with JBOSS management endpoint.
      • All org.jboss.remoting3.remote.RemoteConnectionHandler objects lingering around are associated with Remote Endpoint Name "cli-client". which is the endpoint name used by org.jboss.as.cli.

      Above observations seem to indicate that JBOSS CLI commands that are executed periodically in this deployment, to monitor status of deployments, is causing these stale objects.

      To confirm this observation, we have executed jboss-cli.sh a couple of times on our deployment and could see that each execution of this script is leaving nehind one instance of each of these classes.

      Wildfly version details:
      bash-4.4# ./jboss-cli.sh
      You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
      [disconnected /] connect
      [standalone@localhost:9990 /] version
      JBoss Admin Command-line Interface
      JBOSS_HOME: /ericsson/3pp/wildfly
      Release: 9.0.1.Final
      Product: WildFly Full 17.0.0.Final
      JAVA_HOME: /usr/
      java.version: 1.8.0_222
      java.vm.vendor: IcedTea
      java.vm.version: 25.222-b10
      os.name: Linux
      os.version: 4.12.14-197.15-default

      Attachments

        Activity

          People

            Unassigned Unassigned
            nvinothkumar Vinoth Kumar Natarajan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: