[jboss-jira] [JBoss JIRA] Commented: (JBAS-3748) give run.sh the ability to run the VM in background and export the PID as an env. var.

[John Mazzitelli (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3748?page=comments#action_12344768 ] 
            
John Mazzitelli commented on JBAS-3748:
---------------------------------------

One other idea that would work (and would allow us to execute run.sh normally rather than just source it) is to not pass JBOSS_PID variable, but instead have the value of LAUNCH_JBOSS_IN_BACKGROUND be set to a file path by whoever is executing run.sh.

If LAUNCH_JBOSS_IN_BACKGROUND is set, assume its a full filepath and use it as the filename to store the pid.  run.sh can be executed normally and will write the pid thus allowing init.d to pick it up.

Dimitris also had an idea to avoid setting variables at all and just have a signal trap in the run.sh set up so that when run.sh process is killed, it forwards that signal to the VM process - effectively killing the JBossAS process too.  This would involve more testing since I've seen strange signal trap behavior on some platforms.  We need to test this signal trap stuff on all flavors of UNIX as well as Darwin and Cygwin.

> give run.sh the ability to run the VM in background and export the PID as an env. var.
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-3748
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3748
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.0.5.CR1
>            Reporter: John Mazzitelli
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.0.5.GA
>
>         Attachments: patch.txt
>
>
> I want to write an init.d script with the typical start - stop options to start JBossAS. I want to use the method of writing a pid file when started and killing the pid found in the file when stopping.
> I do not want to use the "normal" shutdown mechanism to stop it because that assumes the JBoss instance has exposed its remote MBean interface (and I do not want to assume that). Plus, I want to ensure it is killed, and using the "kill" command is as fool-proof as I need it to be.
> I also want to be able to use run.sh to start the instance (I do not want to have to do all the work run.sh does - setting up the JVM, passing in arguments, worrying about all the cygwin - darwin things, etc. etc.).
> But, if my init.d script starts run.sh, I cannot use $! in my init.d script as the pid file contents because $! is the pid of run.sh script process. It is NOT the pid of the JBoss JVM instance itself. If I then go to kill the run.sh process, it dies, but the JVM process does not. Therefore, the init.d stop option does not work - it cannot stop the JBoss VM.
> I would like to propose to make the following change to run.sh that would facilitate this. This change is backwards compatible. What this change does is - if I set the environment variable "LAUNCH_JBOSS_IN_BACKGROUND" and source run.sh, run.sh will export JBOSS_PID as the pid value of the JVM process. My init.d script (the thing that sources run.sh) will be able to write JBOSS_PID anywhere I want and thus later be able to use it to kill the JBoss VM.
> See attached patch for the change.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira