Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7295

org.jboss.system.server.jmx.JMXKernel exposes empty methods for invocation through jmx console

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.1
    • JMX
    • None

    • JBoss Enterprise Application Platform (EAP) 5

    • Hide

      1) Log in to jmx-console and follow the "type=Server" link under the jboss.system section
      2) Invoke runGarbageCollector method
      3) Verify in gc logging that no GC took place

      Show
      1) Log in to jmx-console and follow the "type=Server" link under the jboss.system section 2) Invoke runGarbageCollector method 3) Verify in gc logging that no GC took place
    • Release Notes
    • Hide
      The traceInstructions, traceMethodCalls, runGarbageCollector and runFinalization methods in org.jboss.system.server.jmx.JMXKernel were empty. Calling these methods was therefore successful, but no operation was actually performed by them. The code of the methods has been extended to call the alike named methods in java.lang.Runtime. The methods are now no longer empty and the expected operations are performed when the methods are called.
      Show
      The traceInstructions, traceMethodCalls, runGarbageCollector and runFinalization methods in org.jboss.system.server.jmx.JMXKernel were empty. Calling these methods was therefore successful, but no operation was actually performed by them. The code of the methods has been extended to call the alike named methods in java.lang.Runtime. The methods are now no longer empty and the expected operations are performed when the methods are called.
    • Documented as Resolved Issue
    • NEW

    Description

      Following the "type=Server" link under the jboss.system section of the jmx-console, there are several methods that appear to do nothing (traceInstructions, traceMethodCalls, runGarbageCollector, runFinalization). Invoking them returns the result on the page "Operation completed successfully without a return value!" But nothing is done. It looks like the issue is several empty methods in org.jboss.system.server.jmx.JMXKernel. These worked in EAP 4.3, which relied on org.jboss.system.server.ServerImpl for this functionality. Looks like functionality was not fully ported over to the new JMXKernel class that took its place.

      Attachments

        Activity

          People

            rhn-support-aogburn Aaron Ogburn
            rhn-support-aogburn Aaron Ogburn
            Petr Penicka Petr Penicka (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: