[jbosstools-issues] [JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter

Martin Malina (JIRA) issues at jboss.org
Fri Oct 31 09:47:35 EDT 2014


     [ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina resolved JBIDE-17212.
-----------------------------------
    Fix Version/s: 4.2.0.Final
                       (was: 4.2.x)
       Resolution: Cannot Reproduce Bug


I tried this now and it works (JBDS 8.0.0.GA).
Here's what I did:
Deploy-only server
Startup script: "read"
Shutdown script: <empty>

As expected, first attempt to stop the server failed and second attempt killed the process and the server was then marked as Stopped.

> Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-17212
>                 URL: https://issues.jboss.org/browse/JBIDE-17212
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Final
>
>
> As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case.
> From JBIDE-7515:
> {quote}
> I left the shutdown script empty.
> You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't.
> In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1".
> {quote}
> The shutdown should default to process kill even if the shutdown script is empty.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbosstools-issues mailing list