[Wrapper-user] Service started with Java Service wrapper becoming stale during server reboot

[Divya H. <div...@gm...>]

I have few services that are running in a Linux machines and I am using the
3.2.3 version of  http://old.nabble.com/file/p33441896/Poller.conf
Poller.conf Java Service Wrapper. Just before the sever reboot, the services
are stopped using a stopall services command(that has stop command for each
service).While Few services are giving out the  following warning ::
 'WARN   | wrapper  | 2012/03/04 03:00:42 | JVM process was still running
after receiving a SIGCHLD signal.
STATUS | wrapper  | 2012/03/04 03:00:42 | TERM trapped.  Shutting down.'

After the sever reboot, a startall application script(that has start command
for each service) is run.It starts all the applications except those that
gave the above warning.

But when I try starting the service again using the start command of that
particular service, it starts with the message '"Removed stale pid file:' .

I want to understand here two things:
1.Why the process has become stale.
2.Why the start all application command that had the start command didn
start it after removing the stale id.

I am attaching the configuration file.

Thanks in advance.


-- 
View this message in context: http://old.nabble.com/Service-started-with-Java-Service-wrapper-becoming-stale-during-server-reboot-tp33441896p33441896.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.