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 <[EMAIL PROTECTED]>: > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
