I made a change to a jar file for a web app and uploaded it using my
normal process. Immediately after refreshing the jar on the server,
Tomcat went into an infinite loop restarting the app (See snippit from
stdout log below).
Any ideas what could have caused this? I erased the jars and
re-uploaded but the problem continues
Is there any way to specify that tomcat should simply give up if an
app doesn't start after 'n' tries within a couple of minutes?
I'm on Tomcat 6.0.13
30-nov-2007 21:23:23 org.apache.catalina.loader.WebappClassLoader modified
INFO: Additional JARs have been added : 'jep-2.3.0.jar'
30-nov-2007 21:23:23 org.apache.catalina.core.StandardContext
reload
INFO: Reloading this Context has started
30-nov-2007 21:23:33 org.apache.catalina.loader.WebappClassLoader modified
INFO: Additional JARs have been added : 'jep-2.3.0.jar'
30-nov-2007 21:23:33 org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
30-nov-2007 21:23:43 org.apache.catalina.loader.WebappClassLoader modified
INFO: Additional JARs have been added : '
jep-2.3.0.jar'
30-nov-2007 21:23:43 org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
...........................................
Thanks,
David Sánchez
