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 there was a general problem with the app. Anyone know a good generic way to check that an app has at least managed to initialise ok. Cheers -- View this message in context: http://www.nabble.com/generic-way-of-checking-application-status--tf4850640.html#a13878725 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 elements. This could be used to provide a more elegant way of receiving notification of when the server has stopped. However, still not synchronous, looking at JMX for that, seems like I just need to invoke StandardServer.stop() Christopher Schultz-2 wrote: Is there a synchronous method for stopping Tomcat, i.e. one that won't return until the ports have been released at least? Not that I know of. Lots of folks have posted to the list somewhat recently asking basically the same question: how do you know when Tomcat has really stopped? The best hack I've heard of is to watch the catalina.out log file for the magic Tomcat Stopped message. Another option would be to actually poll the port to see if it's available. They're both pretty ugly options. - -chris -- View this message in context: http://www.nabble.com/synchronous-stop-of-tomcat-tf4392954.html#a12553588 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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). Server ... Listener ... / ... 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 job done though. you you could touch a file or something like that. That would be a nice simple way of doing it. Will give that a shot on Monday. Cheers, Derek -- View this message in context: http://www.nabble.com/synchronous-stop-of-tomcat-tf4392954.html#a12558158 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 that won't return until the ports have been released at least? Cheers, Derek -- View this message in context: http://www.nabble.com/synchronous-stop-of-tomcat-tf4392954.html#a12525265 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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, it wouldn't request state from another, would it ?:) Indeed, using lsof and ps I found there was a 'ghost' tomcat instance running. Killed that and all is well. -- View this message in context: http://www.nabble.com/Error-reported-when-starting-app-in-cluster-tf4212847.html#a12016178 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 distributable/ 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 reported that might keep your application from comin' up well. No other problems reported. This error appears at the beginning of the application's log then afterwards it continues and starts the application without problem. I can then go on to use the application. Haven't tested whether session replication is working yet, but this doesn't inspire confidence. Sounds like it is not normal to see this, so will check my cluster configuration. Cheers, D. -- View this message in context: http://www.nabble.com/Error-reported-when-starting-app-in-cluster-tf4212847.html#a11984950 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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-03 15:12:25,796 36 [main] WARN org.apache.catalina.cluster.session.DeltaManager - Manager [/123/456/789], requesting session state from org.apache.catalina.cluster.mcast.McastMember[tcp://192.168.0.1:12345,catalina,192.168.0.1,12345, alive=20829629727]. This operation will timeout if no session state has been received within 60 seconds. 2007-08-03 15:13:25,853 60093 [main] ERROR org.apache.catalina.cluster.session.DeltaManager - Manager [/123/456/789]: No session state send at 03/08/07 15:12 received, timing out after 60,086 ms. Thanks, D. -- View this message in context: http://www.nabble.com/Error-reported-when-starting-app-in-cluster-tf4212847.html#a11984296 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 is no error recorder, last line is: INFO: Manager: Uploading WAR file to /CATALINA_BASE/webapps/123/456/789.war The war file is now there on the server. (although this much only works so long as I created the dirs in advance) If I try a more simple context path, e.g. path=/789 war=file:789.war, the deploy goes just fine. Is it not possible to deploy apps with paths like /123/456/789 using the manager, or am I perhaps doing something wrong? Cheers, D. Please access the attached hyperlink for an important electronic communications disclaimer: http://www.lse.ac.uk/collections/secretariat/legal/disclaimer.htm - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
