tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Gomez <henri.go...@gmail.com>
Subject Re: bugs 34140 and 34199
Date Thu, 21 Apr 2005 10:04:37 GMT
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 disactivated by conf) and
destroyed just before Tomcat stop. And if you could get the initial
process/job id and pass it to tomcat, it could fill this fill with
such jobid.

2005/4/21, jean-frederic clere <jfrederic.clere@fujitsu-siemens.com>:
> 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
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message