[
https://issues.jboss.org/browse/JBIDE-17020?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-17020.
---------------------------------
Resolution: Done
I've tried this on two systems. Seems the logic I used to get the remote pid was
slightly incorrect in string parsing. I was expecting the returned string to start with my
custom string, but, sometimes the shell prompt is before my expected string. It's been
fixed.
EAP process on remote server is not terminated when you abort a
server startup
------------------------------------------------------------------------------
Key: JBIDE-17020
URL:
https://issues.jboss.org/browse/JBIDE-17020
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Environment: JBDS 8.0.0.Beta1a B82
EAP 6.2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.CR1
When you set up a remote server (e.g. eap 6.2) with management (without a runtime, but
that shouldn't really matter here) and during startup fail to enter the correct
credentials the server is stuck on Starting. If you then press the Stop button twice, the
server will be shown as stopped, but in fact the process will still be running on the
server. This is a bug - the process should be terminated / killed in this case.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)