Metawerx Java Hosting Small Logo

Debug Your App - LifecycleException

This page shows errors where a LifecycleException exception is thrown and how to fix them.

Table of Contents

LifecycleException: Manager has not yet been started

Submitter: Neale Rudd
Dec 6, 2006 11:55:28 PM org.apache.catalina.core.StandardContext reload
SEVERE: Cannot find message associated with key standardContext.stoppingContext
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.reload(StandardContext.java:3037)
        at org.apache.catalina.startup.HostConfig.restartContext(HostConfig.java:873)
        at org.apache.catalina.startup.HostConfig.checkContextLastModified(HostConfig.java:759)
        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(LifecycleSupport.java:119)
        at org.apache.catalina.core.StandardHost.backgroundProcess(StandardHost.java:800)
        ...
This is usually followed by the following when Start is clicked in the Tomcat Manager:
INFO: Container StandardContext[] has already been started

This error occurs when reloading a Tomcat application.

The best way to reload an application is to simply modify web.xml and have the autoDeploy feature redeploy the application for you, or to use the Reload link in the Tomcat Manager.

The error has been observed to happen when the Stop link is pressed in the manager, or when Tomcat is already trying to deploy the application. For example:

  • Start is clicked twice, instead of the user waiting for the first response to complete
  • Start or Reload is clicked when autoDeploy is already deploying the application

The bug is supposed to be fixed in Tomcat 5.0.28 and Tomcat 5.5. However, we have seen it happen on 5.0.28, and have re-opened the bug in the Tomcat bugzilla database.

If you see this happen in Tomcat 5.5.x, please update or comment on this page, and notify the Tomcat developers by updating the bugzilla bug listed above.

navigation
metawerx specific
search
Share
tools
help

referring pages

Share