tomcat cannot refresh my webapps

[charly]

Greetings all !

I've installed Tomcat 4.1.27 and it works great excepted for a little
tiny problem :

In my server.xml, I did configure my context like this :
<Context path="/myApp" docBase="myApp" debug="0" reloadable="true"
crossContext="true"/>

If I modify a bean or a servlet, Tomcat says :


WebappClassLoader: Resource '/WEB-INF/classes/bean/BeanDossier.class'
was modified; Date is now: Sun Dec 07 13:19:37 CET 2003 Was: Sat Dec 06
22:48:44 CET 2003

So it would seem that everything is ok

BUT when I refresh or try to navigate in my web Application : I get
errors (lengthy) :

javax.servlet.ServletException: L'enrobeur (wrapper) ne peut trouver la
classe servlet mvc.Controller ou une classe dont elle dépend
My translation -> Wrapper cannot find the mvc.controller class or a
class whom she depends on
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:891)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:536)

cause mère

java.lang.ClassNotFoundException: mvc.Controller
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1444)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1289)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:885)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:536)

If I stop my server and restart it, everything is fine.

Any ideas ?

 

[William Brogden]

Greetings all !

I've installed Tomcat 4.1.27 and it works great excepted for a little
tiny problem :

Did you install the Hotfix for 4.1.27 - it has to do with a reloading bug.

 

[charly]

No I didn't. Maybe I'd better swap to Tomcat 5 or better yet, Jetty ?

 

[Andy Fish]

tomcat 4.1.29 is the latest production version of tomcat 4.1, and it does
not have the reloading bug

 

[im2kul[at]comcast[dot]net]

tomcat 4.1.29 is the latest production version of tomcat 4.1, and it does
not have the reloading bug

Tomcat 5.0.16 was announced to be stable (read: production version) on December 3rd, 2003:

http://jakarta.apache.org/site/news.html#20031203.1

 

[Mike]

I browsed through the Tomcat source code a few times, and didn't think
it was put together very well. I find Jetty far more straightforward
and cleaner.

For JBoss for instance, I always pick the Jetty flavoured one, which I
find I have less problems with.

Tomcat should be seen as such a 'defacto' implementation. In fact, a
lot of the Apache code is pretty weak. Have you seen the Xerces code?
Oh my frigging code what the hell is that...