Re: generic way of checking servlet status?

Have considered this a bit further, seems the first step would be to mark the Servlet as unavailable by ensuring init throws an UnavailableException. But then what? As far as I can see there is no way to check if a Servlet is unavailable using Tomcat's built in MBeans. Is this true?

generic way of checking application status?

Deploying an app with a runtime dependency missing resulted in Servlet.init() throwing a ServletException caused by a ClassNotFoundException. Tomcat manager however reported the application as running. I guess it was to a certain extent, however it would have been more useful to me to know that t

Re: synchronous stop of tomcat

I was meaning that it appears you can add a listener directly to the Server element (AFAIU from the code anyway). ... > Not synchronous? Aren't notifications almost always synchronous? Yes, the notification would be synchronous but the call to stop is still asynchronous. Would get the

Re: synchronous stop of tomcat

Have been looking at the source, although not documented (for TC5.5), it seems that it is possible to nest a Listener element (org.apache.catalina.LifecycleListener) under the Server element as http://tomcat.apache.org/tomcat-5.5-doc/config/context.html described here for nesting within Context e

synchronous stop of tomcat

Using: $CATALINA_HOME/bin/catalina.sh stop $CATALINA_HOME/bin/catalina.sh start in quick succession to restart Tomcat, it is possible that the start operation will run before all ports have been released by the instance I'm stopping. Is there a synchronous method for stopping Tomcat, i.e. one th

Re: Error reported when starting app in cluster

Filip Hanik - Dev Lists wrote: > > Derek Alexander wrote: >>> the same app would have to run on both instances, >>> >> >> You mean this error is normal when starting the first server in a >> cluster? >> > if it was the first server,

Re: Error reported when starting app in cluster

> the same app would have to run on both instances, You mean this error is normal when starting the first server in a cluster? -- View this message in context: http://www.nabble.com/Error-reported-when-starting-app-in-cluster-tf4212847.html#a11985035 Sent from the Tomcat - User mailing list a

Re: Error reported when starting app in cluster

> Does this application run well in a tomcat that isn't clustered? Yes > Does your application have the element in web.xml? Yes > I'd recommend looking through the output in the other log files in > $CATALINA_HOME/logs/, especially localhost, to see whether there are > any exceptions / errors

Error reported when starting app in cluster

Getting an ERROR reported when starting webapp within a cluster. Note, at this time I am starting the first server in the cluster, which is the 192.168.0.1 mentioned in the error message. Can someone please explain if it is correct that I am receiving an error and if so, what is wrong. 2007-08

RE: Using manager to deploy with path="/123/456/789"

Thanks for the replies. Yes, we're doing it the manual way currently, but were hoping to use the manager to streamline our deployment processes. I've opened a couple of issues, first asking for a decent error message, second requesting this feature be added: http://issues.apache.org/bugzilla/sh

Using manager to deploy with path="/123/456/789"

Hi, I want to use the manager to deploy an app with the context path like /123/456/789 If I use the manager path="/123/456/789" war="file:789.war" it doesn't work. At the client end (ant) I'm seeing: FAIL - Failed to deploy application at context path /123/456/789 In the logs on server, there