Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-3947

JConsole throws exception on connect post JBoss4.0.3SP1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2
    • JBossAS-4.0.4.CR2, JBossAS-4.0.4.GA, JBossAS-4.0.5.CR1, JBossAS-4.0.5.GA
    • None
    • None
    • Workaround Exists
    • Hide

      Going to the JMX console and manually selecting the java.lang:type=Runtime MBean seems to allow JConsole to access the host. I would assume that the appropriate classes are being loaded manually which allows the connection to succeed.

      Show
      Going to the JMX console and manually selecting the java.lang:type=Runtime MBean seems to allow JConsole to access the host. I would assume that the appropriate classes are being loaded manually which allows the connection to succeed.

      In JBoss 4.0.3SP1 JBoss allowed connecting via the JConsole utiltiy provided with the JDK. As of JBoss 4.0.5 this no longer works on startup and requires user action to complete effectively. I have posted a stack trace to this issue. It appears that the java.lang:type=Runtime MBean is no longer being registered at startup which causes the connection to fail when it cannot locate this MBean.

      I tested this in the following configurations:

      JBoss 4.0.3SP1 (successful)
      JBoss 4.0.5GA (fails)
      JBoss 4.2CR1 (fails)

        1. jconsole-trace.txt
          6 kB
        1.
        		 Need to expand the jmx console tests to validate accessing the jdk mbeans Sub-task Closed Major Scott Stark (Inactive)

            starksm64 Scott Stark (Inactive)
            weston.price Weston M. Price (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: