0 Replies Latest reply on Nov 16, 2012 5:29 PM by mikevan

    Strange lack of exception when attempting to deploy an .ear containing a .war file.

    mikevan Newbie

      When attempting to deploy an .ear containing a .war file, I get the following message:

      6:34:42,613 TRACE [org.jboss.modules] (MSC service thread 1-4) Defined class org.apache.xerces.parsers.AbstractSAXParser$LocatorProxy in Module "org.apache.xerces:main" from local module loader @4470a4a6 (roots: /home/blue/DEV_TOOLS/jb

      oss-as-7.2.0.Alpha1-SNAPSHOT/modules)

      16:34:42,615 TRACE [org.jboss.modules] (MSC service thread 1-4) Attempting to find all resources META-INF/web-fragment.xml in Module "deployment.myapp.ear.web-myApp:main" from Service Module Loader

      16:34:42,616 TRACE [org.jboss.jca.core.api.connectionmanager.ccm.CachedConnectionManager] (MSC service thread 1-4) popped object: org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManag

      erSetupAction@1b173b2b

      16:34:42,616 ERROR [org.apache.catalina.core] (MSC service thread 1-4) JBWEB001103: Error detected during context /startApp start, will stop it

       

      However even with the logging on TRACE, and then ALL, the only exceptions are produced by hornetq.  Can someone please point me in the right direction?  I have a web.xml document in the .war file's WEB-INF directory and that configuration worked well in 4.2.2, but not in 7.2.0.