[ https://issues.jboss.org/browse/JBIDE-12770?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-12770. --------------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.Beta1) Resolution: Done committed to cr1. The error is logged in the error log view, and the view stops trying to load the mbeans. Unfortunately, the "error" node in the view is not showing, so I'll open a bug for that. This would be a more obvious clue for the user that something went wrong, and what it was. -- 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

[ https://issues.jboss.org/browse/JBIDE-12770?page=com.atlassian.jira.plugi... ] 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. -- 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