[
https://issues.jboss.org/browse/JBIDE-12770?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-12770.
---------------------------------
Resolution: Done
Hi Martin:
Those error messages are simply there to help users discover what MIGHT have gone wrong.
So I try to handle the exceptions I know I can. And for the ones I can't, I simply
give advice.
ANd yes, it is intended that if the connection attempt fails, we log the error, and stop
re-trying. The retrying was what was causing the eclipse crash. So avoiding that was
priority-1. The rest is make sure a proper error is logged.
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