Hi,

We're using tomcat 4.0.3 on our production server and there seems to be
some odd behaviour with the automatic reloading of contexts. This is
what happens:

1. A reload of the context is triggered because of an update of the code
on the server (via ftp upload).
2. A servlet gets marked as "unavailable" because the class-loader can't
find the necessary class (eg the appropriate jar file with the servlet
isn't present yet).
3. The necessary jar file ends up on the server.
4. The context reloads again and the servlet in question starts-up
automatically
(<load-on-startup>0</load-on-startup>), generating logs and other
infromation that clearly indicate it has started correctly this time.
5. The servlet stays unavailable (503 errors get reported) according to
Tomcat.

Is there a known issue with servlets marked as "unavailable" not coming
back (available) after an automatic reloading of the context?

A more general question: what would be the best reloading scenario on a
production server? We're in a case where the developper that needs to
redeploy an application can't restart tomcat. We're using virtual hosts
as well, so the manager application seems insufficiënt.

Regards,
Thomas Goorden


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)