Hi:
We resolved this my running tomcat as a daemon process. There are instructions
at the tomcat site regarding how to do this. Once tomcat was running as a
daemon process, when the Jenkins job terminated that started the tomcat
application server, the tomcat application server stayed running.
On Thursday, January 22, 2015 11:20 AM, Eric Wood
<eric.w...@rocketmail.com> wrote:
I'm attempting to start a tomcat server via the publish over ssh plugin.
I call a shell script as follows:
sudo nohup /apps/Config/usr/local/bin/ec2-init env start > /dev/null
2>&1 &
This script in turn calls the following: ec2-init > tomcat_sdb > startup.sh >
catalina.sh.
Our IT guy set the following in the script tomcat_sdb:
# Protection from Jenkins ProcessTreeKiller BUILD_ID=dontKillMe
export JAVA_HOME JAVA_OPTS PATH CUSTIDAPPID INSTANCEID JBOSS_SERVER BUILD_ID As
soon as the Jenkins job terminates I can see the catalina process die.
What is the proper way to invoke this environment variable to keep the tomcat
process alive after Jenkins terminates?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1423634528.3086904.1421943611888.JavaMail.yahoo%40jws100100.mail.ne1.yahoo.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/183543886.345048.1422283418158.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.
