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

Rob Stryker (JIRA) issues at jboss.org
Wed Jul 2 05:01:25 EDT 2014


    [ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981292#comment-12981292 ] 

Rob Stryker commented on JBIDE-17212:
-------------------------------------

I'm not able to replicate this.

Steps:  
  1) Create a shell script with whatever you want in it, long running task.  In my case, I put the following:

{code}
#!/bin/sh
java "-Dprogram.name=JBossTools: WildFly 8.x" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.0.0.Final.zip.expanded/standalone/log/boot.log" "-Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.0.0.Final.zip.expanded/standalone/configuration/logging.properties" "-Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.0.0.Final.zip.expanded" -Dorg.jboss.logmanager.nocolor=true  -jar /home/rob/apps/jboss/unzipped/wildfly-8.0.0.Final.zip.expanded/jboss-modules.jar  -mp "/home/rob/apps/jboss/unzipped/wildfly-8.0.0.Final.zip.expanded/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml
{code}

2)  give your shell script execution rights.   (chmod +x test1.sh)
3)  create a deploy-only server
4)  modify launch command to be /home/rob/scripts/test1.sh
5) Verify shutdown script is empty
6) save changes, start server
7) ps ax | grep "test1.sh"
8) verify process is shown
9) shutdown server
   9a) shutdown fails, bc no stop script. Next stop attempt will force-term
10) shutdown server again
11) verify console shows a stopped process
12)  ps ax | grep "test1.sh"   shows no result, process is dead

Unfortunate side effect:   
    The java process is still running. A termination on the test1.sh process does not kill the child process.   No idea how to handle this. 

> 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.Beta3
>
>
> 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.2.6#6264)


More information about the jbosstools-issues mailing list