]
Rob Stryker updated JBIDE-7608:
-------------------------------
Priority: Critical (was: Major)
this was critical for usability as the thread seemed to have frozen but didn't.
JBossServerConnection (jmx related) executing long-running task after
server status changed to 'started'
--------------------------------------------------------------------------------------------------------
Key: JBIDE-7608
URL:
https://jira.jboss.org/browse/JBIDE-7608
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.2.0.Beta2
The proper class sets server to started, but the job doesn't complete because setting
server state to started fires off to all server state listeners. Setting state to started
(and executing all server state listeners) does not have a progress monitor at all. So
when the JBossServerConnection class tries to access jmx on a remote server that
doesn't have it enabled, it simply seems to freeze the "starting server"
portion.
Answer is to have the JBossServerConnection class (which listens to server state) to fire
off its own job rather than executing in the current thread. This also allows the user to
see what's going on.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: