Uploaded image for project: 'Remoting JMX'
  1. Remoting JMX
  2. REMJMX-45

Memory leak when requesting attributes using JMXConnectorFactory over remoting-jmx via management interface

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.4.Final
    • 1.0.3.Final
    • Connection
    • None
    • Hide

      Run JBoss AS out of the box:

      jboss-as-7.1.1.Final/bin/standalone.sh
      

      Run JBoss jconsole.sh with

      sh -x $JBOSS_HOME/bin/jconsole.sh
      

      then close it.
      This will show in the terminal "CLASSPATH" followed by class path required for remote JMX client (let's call it $JBOSS_JMX_CLASSPATH)

      Download check_jmx Nagios plugin from http://exchange.nagios.org/directory/Plugins/Java-Applications-and-Servers/check_jmx/details

      In the check_jmx directory, run in bash:

      while true; do CLASSPATH=$JBOSS_JMX_CLASSPATH:nagios/plugin/jmxquery.jar timeout -sKILL 5 java org.nagios.JMXQuery -U 'service:jmx:remoting-jmx://localhost:9999' -O java.lang:type=Memory -A HeapMemoryUsage -K used; done
      

      (using "timeout" from coreutils because the command freezes sometimes)

      Heap usage can be seen in JConsole to grow linearly by over 100 Mb/hour and end up using all available heap.

      Show
      Run JBoss AS out of the box: jboss-as-7.1.1.Final/bin/standalone.sh Run JBoss jconsole.sh with sh -x $JBOSS_HOME/bin/jconsole.sh then close it. This will show in the terminal "CLASSPATH" followed by class path required for remote JMX client (let's call it $JBOSS_JMX_CLASSPATH) Download check_jmx Nagios plugin from http://exchange.nagios.org/directory/Plugins/Java-Applications-and-Servers/check_jmx/details In the check_jmx directory, run in bash: while true; do CLASSPATH=$JBOSS_JMX_CLASSPATH:nagios/plugin/jmxquery.jar timeout -sKILL 5 java org.nagios.JMXQuery -U 'service:jmx:remoting-jmx://localhost:9999' -O java.lang:type=Memory -A HeapMemoryUsage -K used; done (using "timeout" from coreutils because the command freezes sometimes) Heap usage can be seen in JConsole to grow linearly by over 100 Mb/hour and end up using all available heap.

      Repeated remote request of JMX attributes, as performed by a Nagios plugin, causes heap space to grow to the limit and eventually the server to freeze.

              darran.lofthouse@redhat.com Darran Lofthouse
              agattik Alexandre Gattiker (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: