my theory is wrong.
--Rob
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Eric Wood
Sent: Tuesday, November 04, 2014 3:51 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Unable to successfully start a JBOSS service using Publish over SSH
An addit
An additional note. I see that they recommend using the provided service
script called $JBOSS_HOME/bin/init.d/jboss-as-standalone.sh. We are using some
"older" version developed in-house. I can't see significant differences, but
not sure if the way the service is invoked is a factor.
do you us
Richard:
When I run the service from the command line on the actual server, it takes
about 30 secs to run and does return to the command line prompt. If I run the
same service from the publish over ssh, it does not seem to return and times
out. I have the time out set to five minutes. It i s
Hi Eric
We do this with JBoss EAP and it works fine. We found we had to up the
"Exec Timeout" property (under Advanced) as the JBoss start script that we
use doesn't return until the app server has started and all the apps
deployed have started too (i.e. its "open for business")
Not sure if thats
The appearance is that as long as the process is running, the ssh session will
not terminate. It will eventually timeout, but not terminate on it own even
when the service command exits with a "0". If I run the command:
service jbossas7.1 stop
while the Jenkins job is still connected an
