Web app deployed in JBoss 3.2.2, won't in 3.2.4

[charleschr]

Hi all,

I have an application EAR file which contains an EJB JAR file and a WAR file. Under JBoss 3.2.2, everything works swimmingly. When trying to upgrade to JBoss 3.2.4 however, the EJB JAR file deploys fine but the WAR file will not deploy. I'm sure there must be some configuration or library change I am missing somehow, but I can't figure out what. If anyone has any ideas for me, I'd appreciate hearing them.

This is the top bit of the console with the stack trace. I can post more if anyone needs to see more:

13:17:05,624 INFO [EJBDeployer] Deployed: file:/F:/jboss-3.2.4/server/myapp/tmp
/deploy/tmp28277myapp.ear-contents/myapp.jar
13:17:06,687 INFO [TomcatDeployer] deploy, ctxPath=, warUrl=file:/F:/jboss-3.2.4/server/myapp/tmp/deploy/tmp28277myapp.ear-contents/myapp.war/
13:17:06,702 ERROR [BaseModelMBean] Exception invoking method destroy
java.lang.NoSuchMethodError
at org.jboss.web.tomcat.tc5.WebCtxLoader.stop(WebCtxLoader.java:109)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4517)
at org.apache.catalina.core.ContainerBase.destroy(ContainerBase.java:1213)
at org.apache.catalina.core.StandardContext.destroy(StandardContext.java:4573)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:109)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:140)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:68)

Thanks,

Chuck

[charleschr]

To add to the weirdness:

If I then hot redploy the EAR file after things fail the first time, the WAR successfully deploys. If I shut down JBoss and restart it, the deployment fails again, but succeeds after another hot redeploy. It seems like my WAR file is being deployed before something else it depends on, but then when I hot redeploy, that dependency has been taken care of.

[charleschr]

The same thing is happening in 3.2.5 as happened in 3.2.4

Charles.

[charleschr]

This was probably pretty obvious to everyone but me, but removing the "ROOT.war" folder from the jbossweb-tomcat50.sar folder under deploy did the trick - there were probably conflicts because we deploy our application under the root context that this WAR was apparently using