1 Reply Latest reply on Jan 29, 2014 5:44 AM by Jagadish M

    Unable to deploy EAR which contains single WAR

    Jagadish M Newbie

      Hi,

       

      I have a problem deploying EAR which contains WAR.  Strange thing is that, I am able to deploy WAR independently without any issues. Due to my org deployment rules, I have to package it as an EAR  to deploy on server.  Jboss doesn’t give much trace of the error which makes it difficult to resolve the exception. 

       

      can someone help me how to increase the log level or what could be issue?

       

      JDK: 1.6.0_45

      Jboss EPA 6.0.1

      Running on Windows 7

       

      09:40:52,794 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-8) Add Service
      id=bgc.services.mobile.ws.impl.DataUsageNotificationPortTypeImpl
      address=http://localhost:8080/dun-ws/DataUsageNotificationPortTypeImpl
      implementor=bgc.services.mobile.ws.impl.DataUsageNotificationPortTypeImpl
      invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
      serviceName={http://impl.ws.mobile.services.bgc/}DataUsageNotificationPortTypeImplService
      portName={http://impl.ws.mobile.services.bgc/}DataUsageNotificationPortTypeImplPort
      wsdlLocation=null
      mtomEnabled=false
      09:40:52,966 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://impl.ws.mobile.services.
      bgc/}DataUsageNotificationPortTypeImplService from class bgc.services.fiona.datausagenotification.v1.DataUsageNotificationPortType
      09:40:53,434 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/dun-ws/Da
      taUsageNotificationPortTypeImpl
      09:40:53,498 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-8) WSDL published to: file:/C:/Users/Public/Documents/Data/
      Jagadish/Softwares/jboss-eap-6.0/standalone/data/wsdl/dtpc-1.0.0.ear/dun-ws.war/DataUsageNotificationPortTypeImplService.wsdl
      09:40:53,548 INFO  [org.jboss.as.webservices] (MSC service thread 1-6) JBAS015539: Starting service jboss.ws.port-component-link
      09:40:53,557 INFO  [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539: Starting service jboss.ws.endpoint."dtpc-1.0.0.ear"."dun-ws.war"."bgc.se
      rvices.mobile.ws.impl.DataUsageNotificationPortTypeImpl"
      09:40:53,557 INFO  [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011907: Register module: Module "deployment.dtpc-1.0.0.ear.dun-ws.war:main" from Servic
      e Module Loader
      09:40:53,568 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-8) register: jboss.ws:context=dun-ws,endpoint=bgc.service
      s.mobile.ws.impl.DataUsageNotificationPortTypeImpl
      09:40:53,817 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-8) Error listenerStart
      09:40:53,817 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-8) Context [/dun-ws] startup failed due to previous errors
      09:40:53,830 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.web.deployment.default-host./dun-ws: org.
      jboss.msc.service.StartException in service jboss.web.deployment.default-host./dun-ws: JBAS018040: Failed to start context
              at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:94)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-re
      dhat-2]
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [rt.jar:1.6.0_05]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [rt.jar:1.6.0_05]
              at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_05]

      09:40:54,043 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "dtpc-1.0.0.ear"
      09:40:54,045 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
      JBAS014777:   Services which failed to start:      service jboss.web.deployment.default-host./dun-ws: org.jboss.msc.service.StartException in service jboss
      .web.deployment.default-host./dun-ws: JBAS018040: Failed to start context

      09:40:54,063 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
      09:40:54,063 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
      09:40:54,064 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started (with errors) in 6683ms - Start
      ed 248 of 335 services (2 services failed or missing dependencies, 84 services are passive or on-demand)

       

      application.xml

       

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
      <application>
          <display-name>DataUsageNotification</display-name>
          <description>DataUsageNotification Application</description>
          <module>
           <java>dun-ws.war</java>
       </module>     
      </application
      

       

       
      jboss-deployment-structure.xml

      
      <?xml version="1.0" encoding="UTF-8"?>
      <jboss-deployment-structure>
       <deployment>  
        <exclusions>
              <module name="org.apache.log4j"/>
              <module name="org.slf4j"/>
           </exclusions>
       </deployment>
       <sub-deployment name="dun-ws.war">  
        <exclusions>
              <module name="org.apache.log4j"/>
              <module name="org.slf4j"/>
           </exclusions>
       </sub-deployment>
      </jboss-deployment-structure>