[jbosstools-issues] [JBoss JIRA] (JBIDE-12770) MBean Explorer causes Eclipse crash when exposing management port but not using management poller

Martin Malina (JIRA) jira-events at lists.jboss.org
Fri Nov 16 10:40:21 EST 2012


    [ https://issues.jboss.org/browse/JBIDE-12770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734921#comment-12734921 ] 

Martin Malina commented on JBIDE-12770:
---------------------------------------

So you're saying the connection failed in this case? I wonder why. If I did use AS7 management startup poller it would work. So if I don't use it it automatically fails? Why is that? It seems it wasn't even attempted, no?

The way I understood this issue is that only if you use the as7 management startup poller the connection is being attempted at all. If you have a web port poller then the jmx connection is not even attempted and you cannot connect to the server in MBean Explorer (but before your fix the MBean explorer thought the connection was active the it crashed eclipse).

So I assumed that the intention is for the mbean explorer to work even if you don't use the as7 management poller, am I wrong?

Anyway, if you think this is the way it's gonna be then I don't really wanna argue that - this is an edge case as I see it so as long as Eclipse doesn't crash it's not really a big deal.
                
> MBean Explorer causes Eclipse crash when exposing management port but not using management poller
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12770
>                 URL: https://issues.jboss.org/browse/JBIDE-12770
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jmx
>    Affects Versions: 4.0.0.Alpha2
>         Environment: JBT 4.0.0.Alpha2b
> OS X 10.8 Mountain Lion
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.Beta2
>
>
> Under specific conditions Eclipse can crash/take 100% CPU. We've seen this before and it happened when there was no JMX connection but the MBean Explorer was trying to load the nodes anyway. This is a similar case. It would be good to have some sort of check before we start loading the MBeans.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list