[jboss-jira] [JBoss JIRA] Commented: (JBAS-6185) JBoss MBeans in JConsole no longer works

[Seva Popov (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12515471#action_12515471 ] 

Seva Popov commented on JBAS-6185:
----------------------------------

Hello Scott, 

I wasn't execting the fix to be in 5.1.0.GA and I saw that it is fixed starting with JBossAS-6.0.0.M1. 

That's why I fixed/patched my installation of 5.1.0.GA exactly as it was described in this bug.

The solution almost worked but with some issues. 

Basically, a remote connection to a JBossAS instance  with jconsole from Sun Java 1.5 works great. I can access all jconsole tabs and on the MBean tab I can see both JVM and JBoss MBeans together. 

But the remote connection to the same JBossAS instance  with jconsole from Sun Java 1.6 only gives access to the MBeans tab. The rest of the jconsole's tab are greyed out.

As I've mentioned I am running JBoss AS on Sun Java 1.6

So, I am curious whether you've tested your fix on Sun Java 1.6 with a remote JMX. I have not seen this in the comments. That's why I thought Jira would be more preferable than the forum in this case.

But I can continue on the forum as you've pointed out.

Thanks for reply,
--Seva


> JBoss MBeans in JConsole no longer works 
> -----------------------------------------
>
>                 Key: JBAS-6185
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6185
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: JBossAS-5.0.0.CR2
>         Environment: JBossAS-5 CR2, Sun Java 1.5, Windows 2003
>            Reporter: jaikiran pai
>            Assignee: Scott Marlow
>            Priority: Blocker
>             Fix For: JBossAS-6.0.0.M1
>
>
> Displaying of JBoss MBeans in JConsole as explained here http://www.jboss.org/community/docs/DOC-10521 , no longer works because of the classpath issue. Maybe related to the refactoring of org\jboss\system\server\jmx\* classes into jboss-system-jmx.jar in JBoss-5.
> More details about this issue can be found in the linked forum thread.

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