1 2 Previous Next 19 Replies Latest reply on Apr 19, 2013 12:26 AM by prashamsjain

    Deployment of EAR and WAR both making trouble but only war is working

    prashamsjain Newbie

      Hi,

       

      I am trying to deploy ear and war file on the jboss 7 but is throwing this execption but not any further detail.

       

      06:47:11,620 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error listenerStart

      06:47:11,620 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/applicationName] startup failed due to previous errors

      06:47:11,636 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001:

      Failed to start service jboss.web.deployment.default-host./applicationName:

      org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./applicationName:

      JBAS018040: Failed to start context        

           at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)       

           at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]        

           at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]        

           at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]        

           at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]        

           at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]

        • 1. Re: Deployment of EAR and WAR both making trouble but only war is working
          Nicklas Karlsson Master

          Is the WAR inside the EAR? Are there any more stack trace available? Show the structure of the deployments (including libs and deployment descriptors)

          • 2. Re: Deployment of EAR and WAR both making trouble but only war is working
            prashamsjain Newbie

            Hello Nicklas,

             

            War and ear are separate it means there are two files application.front.ear and application.back.war. When try to start the Jboss as7 eap6.0.0 it gives the error shown above. no further stack trace thrown by the server.

             

            I am using a jboss-deplyment-structure.xml in the WEB-INF folder.

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

             

            <?xml version="1.0" encoding="UTF-8" ?>

            <

            jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">

             

             

            <!-- <ear-subdeployments-isolated>false</ear-subdeployments-isolated> -->

             

             

            <deployment>

             

             

            <exclusions

            >

             

            <module name="org.jboss.resteasy.resteasy-jaxrs"

            />

             

            <module name="org.jboss.resteasy.resteasy-jackson-provider"

            />

             

            <module name="org.jboss.resteasy.resteasy-jaxb-provider"

            />

             

            <module name="org.jboss.resteasy.resteasy-atom-provider"

            />

             

            <module name="org.jboss.resteasy.resteasy-cdi"/>

             

            <module name="org.jboss.resteasy.resteasy-jaxrs"/>

             

            <module name="org.jboss.resteasy.resteasy-jettison-provider"/>

             

            <module name="org.jboss.resteasy.resteasy-jsapi"/>

             

            <module name="org.jboss.resteasy.resteasy-multipart-provider"/>

             

            <module name="org.jboss.resteasy.resteasy-yaml-provider"/>

             

            <module name="org.hibernate"/>

             

            <module name="javax.persistence.api"/>

             

            </exclusions>

             

             

            <dependencies>

             

             

            <module name="com.sun.xml.messaging.saaj"/>

             

             

            </dependencies >

             

             

            </deployment>

             

            </

            jboss-deployment-structure

            >

             

            • 3. Re: Deployment of EAR and WAR both making trouble but only war is working
              prashamsjain Newbie

              application.front.ear contains classes/resources related to presentation layer

              application.back.war contains classes/resources realted to service layers

              • 4. Re: Deployment of EAR and WAR both making trouble but only war is working
                Nicklas Karlsson Master

                prashamsjain wrote:

                 

                War and ear are separate it means there are two files application.front.ear and application.back.war.

                application.front.ear contains classes/resources related to presentation layer

                application.back.ear contains classes/resources realted to service layers

                 

                Or do you mean the third alternative, application.front.war and application.back.ear (which would sound more natural) ? ;-)

                 

                Which is deployed first? Which one fails?

                • 5. Re: Deployment of EAR and WAR both making trouble but only war is working
                  prashamsjain Newbie

                  Hello Nicklas, pls find the compleet stack trace. I believe application.front.ear is deploying first and creationg error. 09:59:31,111 INFO  [org.jboss.modules] JBoss Modules version 1.1.2.GA-redhat-1 10:00:00,377 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-1 10:00:00,455 INFO  [org.jboss.as] JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) starting 10:03:23,067 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http) 10:03:23,067 INFO  [org.xnio] XNIO Version 3.0.4.GA-redhat-1 10:03:23,114 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA-redhat-1 10:03:23,176 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.8.GA-redhat-1 10:03:23,723 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers 10:03:23,723 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 68) JBAS016200: Activating ConfigAdmin Subsystem 10:03:23,754 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 86) JBAS013101: Activating Security Subsystem 10:03:23,754 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 73) JBAS010280: Activating Infinispan subsystem. 10:03:23,754 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 80) JBAS011800: Activating Naming Subsystem 10:03:23,754 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 81) JBAS011906: Activating OSGi Subsystem 10:03:23,754 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 90) JBAS015537: Activating WebServices Extension 10:03:23,817 INFO  [org.jboss.as.security] (MSC service thread 1-8) JBAS013100: Current PicketBox version=4.0.9.Final-redhat-1 10:03:23,942 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final-redhat-1) 10:03:24,114 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service 10:03:24,192 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default] 10:03:24,551 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 69) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2) 10:03:24,817 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080 10:03:24,942 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/mercuryDataSource] 10:04:01,630 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.4.GA-redhat-1 10:04:14,958 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-eap-6.0\standalone\deployments 10:04:14,958 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "application.front.ear" 10:04:14,958 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "application.back.war" 10:04:14,989 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on 127.0.0.1:4447 10:04:15,005 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on 127.0.0.1:9999 10:07:07,742 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "application.front.war" 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry ${manifest-classpath} in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/barcode4j-fop-ext-complete.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-io-1.3.1.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-logging-1.0.4.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry fop-hyph.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jai_codec.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jai_core.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jimi.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry serializer-2.7.0.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry servlet-2.2.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xalan-2.7.0.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xercesImpl-2.7.1.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xml-apis-1.3.02.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,588 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xmlunit1.0.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/fop-0.94.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxws-api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-impl.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry sjsxp.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-impl.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry stax-utils.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-logging.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/RASR_Proxy.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-httpclient-3.0.1.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/RASR_Transport.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry commons-logging.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/RASR_Transport.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxp-api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jax-qname.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry servlet.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/saaj-impl-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/saaj-impl-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xmlsec.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-api.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-impl.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xmldsig.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:00,603 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry mail.jar in /C:/jboss-eap-6.0/bin/content/application.back.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:01,416 ERROR [stderr] (MSC service thread 1-6) log4j:WARN Continuable parsing error 29 and column 23 10:10:01,416 ERROR [stderr] (MSC service thread 1-6) log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,throwableRenderer?,appender*,plugin*,(category|logger)*,root?,(categoryFactory|loggerFactory)?)". 10:10:04,916 INFO  [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.application.back.war:main" from Service Module Loader 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015850: /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jaxb-api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxb-impl-2.1.7.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jaxws-api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry saaj-api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry saaj-impl.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry sjsxp.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jaxb-api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jaxb-impl.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry stax-utils.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/jaxws-rt-2.1.4.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jaxp-api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry jax-qname.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry servlet.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/saaj-api-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry saaj-api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/saaj-impl-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry activation.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/saaj-impl-1.3.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xmlsec.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry saaj-api.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,947 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry saaj-impl.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,963 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry xmldsig.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:15,963 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015960: Class Path entry mail.jar in /C:/jboss-eap-6.0/bin/content/application.front.ear/application.front.war/WEB-INF/lib/xws-security-3.0.jar  does not point to a valid jar for a Class-Path reference. 10:10:16,166 ERROR [stderr] (MSC service thread 1-1) log4j:WARN Continuable parsing error 29 and column 23 10:10:16,166 ERROR [stderr] (MSC service thread 1-1) log4j:WARN The content of element type "log4j:configuration" must match "(renderer*,throwableRenderer?,appender*,plugin*,(category|logger)*,root?,(categoryFactory|loggerFactory)?)". 10:10:16,447 INFO  [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.application.front.ear:main" from Service Module Loader 10:10:16,853 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-6) Add Service id=com.application.mercury.web.service.scanneddocument.ScannedDocumentWebServiceImpl address=http://localhost:8080/application/online/ScannedDocumentWebService implementor=com.application.mercury.web.service.scanneddocument.ScannedDocumentWebServiceImpl invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={http://application.com/ScannedDocumentService/ScannedDocumentWebService}ScannedDocumentWebService portName={http://application.com/ScannedDocumentService/ScannedDocumentWebService}ScannedDocumentServiceSoapPort wsdlLocation=null mtomEnabled=false 10:10:17,557 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://application.com/ScannedDocumentService/ScannedDocumentWebService}ScannedDocumentWebService from class com.application.mercury.webservice.scanneddocumentservice.ScannedDocumentServiceS oap 10:10:18,150 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-6) Setting the server's publish address to be http://localhost:8080/application/online/ScannedDocumentWebService 10:10:18,322 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-6) WSDL published to: file:/C:/jboss-eap-6.0/standalone/data/wsdl/application.front.ear/application.front.war/ScannedDocumentWebService.wsdl 10:10:18,322 INFO  [org.jboss.as.webservices] (MSC service thread 1-7) JBAS015539: Starting service jboss.ws.port-component-link 10:10:18,338 INFO  [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.application.front.ear.application.front.war:main" from Service Module Loader 10:10:18,338 INFO  [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."application.front.ear"."application.front.war"."com.application.mercury.web.service.scanneddocument.ScannedDocumentWebServiceImpl" 10:10:18,338 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-5) register: jboss.ws:context=application/online,endpoint=com.application.mercury.web.service.scanneddocument.ScannedDocumentWebServiceImpl 10:10:19,666 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Error listenerStart 10:10:19,666 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [/application/online] startup failed due to previous errors 10:10:19,682 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.deployment.default-host./application/online: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./application/online: JBAS018040: Fail ed to start context         at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)         at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]         at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]         at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] 10:10:20,119 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 70) JBAS018559: Deployed "application.front.ear" 10:10:20,119 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 70) JBAS018559: Deployed "application.back.war" 10:10:20,119 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775:    New missing/unsatisfied dependencies:       service jboss.naming.context.java.jboss.resources.jdbc.mercuryDataSource (missing) dependents: [service jboss.naming.context.java.module."application.back"."application.back".env.jdbc.mercuryDataSource] JBAS014777:  Services which failed to start:      service jboss.web.deployment.default-host./application/online: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./application/online: JBAS018040: Failed to start context 10:10:20,166 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 10:10:20,166 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) started (with errors) in 673181ms - Started 728 of 851 services (36 services failed or missing dependencies, 85 services are passive or on-demand)

                  • 6. Re: Deployment of EAR and WAR both making trouble but only war is working
                    Nicklas Karlsson Master

                    deployment.application.front.ear.application.front.war:main

                     

                     

                    So there is a front.war but it's inside front.ear?

                     

                    In any case. You might have some jax-ws libs in your war libs that are interfering...

                    • 7. Re: Deployment of EAR and WAR both making trouble but only war is working
                      prashamsjain Newbie

                      yes there is a application.front.war inside the application.front.ear.

                       

                      and also I can see jaxws-rt-2.1.4.jar inside the both the WAR means application.front.war and application.back.war, so is that the lib which is creating issues.

                      • 8. Re: Deployment of EAR and WAR both making trouble but only war is working
                        Nicklas Karlsson Master

                        Sorry, now I've seen every possible permutation of application(front|back).(war/ear) and I have no idea what is nested where...

                        • 9. Re: Deployment of EAR and WAR both making trouble but only war is working
                          prashamsjain Newbie

                          Hello Nicklas,

                           

                          Greatly appreciate your effort..

                           

                          Can you pl tell me what might be the cause for this error, I will check it further n let you know if found any solution.

                           

                          ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Error listenerStart

                           

                          thanks!!!

                          Prasham

                          • 10. Re: Deployment of EAR and WAR both making trouble but only war is working
                            Nicklas Karlsson Master

                            Show the architecture of your application, e.g.

                             

                            Foo.ear

                                application.xml

                                lib/

                                    Foo.jar

                                Web.war

                                    index.xhtml

                                    WEB-INF

                                        lib/

                                            bar.jar

                            • 11. Re: Deployment of EAR and WAR both making trouble but only war is working
                              prashamsjain Newbie

                              Hello NIcklas,

                               

                              Archilecture of the application is

                               

                              1. application.back.war

                                   a. META-INF

                                            MANIFEST.MF

                                            application.mf

                                   b. WEB_INF

                                             /classes(folder)

                                             /lib(all the JARs)

                                             web.xml

                                             jboss-web.xml

                                   c. log4j.xml

                              2. application.front.ear

                                   a. META-INF

                                             application.xml

                                             MANIFEST.MF

                                   b. log4j.jar

                                   c. log4j.xml

                                   d. application.front.war

                                             /img

                                             /javascript

                                             /META-INF

                                             /steller

                                             /stylesheet

                                             /WEB-INF

                                                  /classes

                                                  /jsp

                                                  /lib

                                                  chain-cofig.xml

                                                  struts-config.xml

                                                  jboss-deployment-structure.xml

                                                  web.xml

                                                  sun-jaxws.xml

                                                  application.tld

                                                
                                            

                              • 12. Re: Deployment of EAR and WAR both making trouble but only war is working
                                Nicklas Karlsson Master

                                OK. Now list the jars in application.back.war/WEB-INF/lib and appliction.front.ear/application.front.war/WEB-INF/lib (there was no ear/lib, right?)

                                • 13. Re: Deployment of EAR and WAR both making trouble but only war is working
                                  prashamsjain Newbie

                                  yes Nicklas,

                                  There is not any lib folder in the ear.

                                  There are 129 jar files in the web-inf/lib folder all of them are related to hibernate, spring, webservice, log4j, struts, commonbeanutils, selenium etc.

                                   

                                  do you want me to list all of them?

                                   

                                  thanks!!

                                  Prasham

                                  • 14. Re: Deployment of EAR and WAR both making trouble but only war is working
                                    Nicklas Karlsson Master

                                    You can either list them or guess yourself which ones are interfering ;-)

                                     

                                    If there are 129 of them, there are bound to be redundant stuff.

                                    1 2 Previous Next