[jbosstools-issues] [JBoss JIRA] (JBIDE-11831) Remote server marked as stopped even if stopped failed
[
https://issues.jboss.org/browse/JBIDE-11831?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11831:
-------------------------------------
Can singleUseShell now be null or is that just an extra guard added
now ?
This was there before and is not new. In reality, this code has not been tested in a
multi-threaded environment, and so it is likely to fail there. The class would likely need
to be revisted to be thread-safe.
As for the situation you just described, further testing is revealing a different patch is
needed. I've discovered a few tiny issues for handling this issue which throw the
workspace into a bit of an uncertain state, even without the patch. So I see this as
pretty important.
Remote server marked as stopped even if stopped failed
------------------------------------------------------
Key: JBIDE-11831
URL: https://issues.jboss.org/browse/JBIDE-11831
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT 3.3.0.Beta3 H152
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: JBIDE-11831.patch
Similarly to JBIDE-11825, when you stop a remote server and the shutdown command fails to
stop the server process for some reason, the tooling will display the server as stopped
even if in fact it is still running.
It the status is Stopped, it should really be stopped.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira