This is an issue with the current tomcat integration not processing war manifest Class-Path references. There is also a problem with trying to stop an already registered mbean. The point at which registration of the web context occurs must be different and this code to try and stop an existing web context needs to be updated. Until the jbossweb integration is done there is not much point in looking at this.


Caused by: LifecycleException:  Manager has not yet been started
        at org.apache.catalina.session.StandardManager.stop(StandardManager.java:659)
        at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4493)
        at org.apache.catalina.core.ContainerBase.destroy(ContainerBase.java:1132)
        at org.apache.catalina.core.StandardContext.destroy(StandardContext.java:4584)
        at org.apache.catalina.core.StandardContext.init(StandardContext.java:5280)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
        ... 84 more

Scott M Stark wrote:
Should not have anything to do with the MC work as this is in a branch. Most likely an issue with the ejb3/tomcat integration code. Let me see what the status of the trunk is.

Anil Saldhana wrote:
Re: [JBoss-dev] error while deploying web application in JBAS 5 beta

Known issue pending Scott's work on classloaders in MC integration.