-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.4.CR2, JBossAS-4.0.4.GA, JBossAS-4.0.5.CR1, JBossAS-4.0.5.GA
-
None
-
None
-
Workaround Exists
-
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)
- relates to
-
JBAS-3978 One off patch for ASPATCH-137: JConsole throws exception on connect post
- Closed
There are no Sub-Tasks for this issue.