unexpected behaviour when hot-deploying

[Rob van Oostrum <ro...@springwellfarms.com>]

On our production environment, when hot-deploying WAR files, Tomcat
occasionally spits out errors like this one:

Mar 29, 2005 12:46:59 AM org.apache.catalina.core.StandardContext
preDeregister
SEVERE: error stopping
LifecycleException:  Manager has not yet been started
        at
org.apache.catalina.session.StandardManager.stop(StandardManager.java:680)
        at
org.apache.catalina.core.StandardContext.stop(StandardContext.java:4496)
        at
org.apache.catalina.core.StandardContext.preDeregister(StandardContext.java:
5415)
        at
org.apache.commons.modeler.BaseModelMBean.preDeregister(BaseModelMBean.java:
1410)
        at
mx4j.server.interceptor.InvokerMBeanServerInterceptor.registration(InvokerMB
eanServerInterceptor.java:160)
        at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.registration(DefaultMB
eanServerInterceptor.java:113)
        at
mx4j.server.interceptor.SecurityMBeanServerInterceptor.registration(Security
MBeanServerInterceptor.java:128)
        at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.registration(DefaultMB
eanServerInterceptor.java:113)
        at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.registration(DefaultMB
eanServerInterceptor.java:113)
        at
mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.registratio
n(ContextClassLoaderMBeanServerInterceptor.java:108)
        at
mx4j.server.MBeanServerImpl.unregisterMBean(MBeanServerImpl.java:1170)
        at
org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:643)
        at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4060)
        at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:8
23)
        at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
        at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
        at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.j
ava:277)
        at
org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
        at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:625)
        at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:431)
        at
org.apache.catalina.startup.HostConfig.checkContextLastModified(HostConfig.j
ava:849)
        at
org.apache.catalina.startup.HostConfig.check(HostConfig.java:1085)
        at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:327)
        at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:119)
        at
org.apache.catalina.core.StandardHost.backgroundProcess(StandardHost.java:80
0)
        at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processC
hildren(ContainerBase.java:1619)
        at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processC
hildren(ContainerBase.java:1628)
        at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(Cont
ainerBase.java:1608)
        at java.lang.Thread.run(Thread.java:534)

Last time this happened a second attempt caused Tomcat to pick up and
successfully deploy the new WAR file. It may be worth noting that Tomcat is
installed on a SAN mount. Could this be triggered by an underlying locking
issue? Any ideas would be most welcome. 

This is Tomcat 5.0.28 running on RHE ES 3.0


Cheers
Rob


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org