e safest way I know around it is not have container based
> shutdown methods on the objects. Instead have a server lifecycle listener
> shut them down using proprietary methods that are not defined by the
> container interfaces (which you should implement as empty methods).
>
> E
>
>
ifecycle of objects.
>
> E
>
>
> - Original Message -
> From: "Anup K Ram"
> To: "Tomcat Users List"
> Sent: Thursday, October 22, 2009 9:38:01 AM (GMT-0800) America/Los_Angeles
> Subject: Re: How to know when tomcat is ready to serve request
>
> T
valve, JNDI resource) or outside the tomcat
> JVM?
>
> E
>
> - Original Message -----
> From: Anup K Ram
> To: users@tomcat.apache.org
> Sent: Wed, 21 Oct 2009 16:56:50 -0700 (PDT)
> Subject: How to know when tomcat is ready to serve request
>
> Hi,
> Is the
Its inside the war file.
On Wed, Oct 21, 2009 at 11:53 PM, Elli Albek wrote:
> Where does the code that needs to know that reside? How is it initialized?
> Is it inside tomcat (war file, valve, JNDI resource) or outside the tomcat
> JVM?
>
> E
>
> - Original Message ---
Hi,
Is there a way to know whether tomcat is started successfully and ready to
serve requests? I need to know this programmatically.
Thanks In Advance.
