[jboss-jira] [JBoss JIRA] Closed: (JBAS-3947) JConsole throws exception on connect post JBoss4.0.3SP1

[Scott M Stark (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3947?page=all ]

Scott M Stark closed JBAS-3947.
-------------------------------

    Fix Version/s: JBossAS-5.0.0.Beta2
                   JBossAS-4.2.0.CR1
                   JBossAS-4.0.5.SP1 
       Resolution: Done
         Assignee: Scott M Stark

> JConsole throws exception on connect post JBoss4.0.3SP1
> -------------------------------------------------------
>
>                 Key: JBAS-3947
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3947
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.0.4.CR2, JBossAS-4.0.5.CR1, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
>            Reporter: Weston Price
>         Assigned To: Scott M Stark
>             Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 
>
>         Attachments: jconsole-trace.txt
>
>
> 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)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira