2005/4/22, Ian F. Darwin [EMAIL PROTECTED]:
Henri Gomez wrote:
I know that but if your starter wrapper check if the process whom pid
is stored on the file is still alive it could determine if the process
has been aborted via kill -9.
I'm using this kind of hack in Linux init.d rc for at
Thanks ;-)
I will do the following:
1 - Add a switch to jsvc to stop the service (doing in C what Henri is doing in
his shell script).
2 - Add a switch to jsvc to wait until the controller process reaches its loop
by doing the following:
create_tmp_file();
while (!stopping) sleep(60); /*
Hi,
Those 2 are reported against Daemon, but the user is looking for a safe way to
know that Tomcat is completly up (AJP connector ready) or completly down. In
jsvc the completly down case is easy: the JVM has exited.
Any hints for the completly up case?
Cheers
Jean-frederic
Many way :
- check the AJP port is listening on the right port.
- Add a 'status' file in AJP support created after AJP is completly up
and destroyed when AJP is closing.
BTW, it will be better to have such file created when Tomcat is fully
started (independant from AJP which could be
Henri Gomez wrote:
Many way :
- check the AJP port is listening on the right port.
- Add a 'status' file in AJP support created after AJP is completly up
and destroyed when AJP is closing.
BTW, it will be better to have such file created when Tomcat is fully
started (independant from AJP which
I know that but if your starter wrapper check if the process whom pid
is stored on the file is still alive it could determine if the process
has been aborted via kill -9.
I'm using this kind of hack in Linux init.d rc for at least 2 years,
whitout problems
2005/4/21, Ian F. Darwin [EMAIL
Henri Gomez wrote:
I know that but if your starter wrapper check if the process whom pid
is stored on the file is still alive it could determine if the process
has been aborted via kill -9.
I'm using this kind of hack in Linux init.d rc for at least 2 years,
whitout problems
Right, if you read
