5 Replies Latest reply on Nov 20, 2015 7:15 AM by jaysensharma

Unable to deploy EAR on JBOSS EAP 6.3

abhi415 Nov 19, 2015 11:19 AM

Hi Developers,

I'm trying to migrate JBOSS EAP 6.3 from websphere. I have successfully installed JBOSS but getting following errors while deploying EAR on JBOSS:

Any suggestions would be highly appreciated:

JBoss Bootstrap Environment

JBOSS_HOME: /usr/local/opt/was/jboss/jboss-eap-6.3

JAVA: /export/home/websphe/java/java_new/jdk1.6.0_101/bin/java

JAVA_OPTS: -server -verbose:gc -Xloggc:"/usr/local/opt/was/jboss/jboss-eap-6.3/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.modules.policy-permissions=true

=========================================================================

08:05:18,213 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1

08:05:18,669 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1

08:05:18,941 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting

08:05:22,153 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.10.GA-redhat-1

08:05:22,169 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

08:05:22,172 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.10.GA-redhat-1

08:05:22,255 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version (unknown)

08:05:22,315 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

08:05:22,329 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem

08:05:22,331 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.

08:05:22,340 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem

08:05:22,352 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension

08:05:22,397 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]

08:05:22,413 INFO [org.jboss.as.security] (MSC service thread 1-7) JBAS013170: Current PicketBox version=4.0.19.SP8-redhat-1

08:05:22,609 INFO [org.jboss.as.connector.logging] (MSC service thread 1-18) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.26.Final-redhat-1)

08:05:22,778 INFO [org.jboss.as.naming] (MSC service thread 1-27) JBAS011802: Starting Naming Service

08:05:22,791 INFO [org.jboss.as.mail.extension] (MSC service thread 1-22) JBAS015400: Bound mail session [java:jboss/mail/Default]

08:05:23,101 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

08:05:23,248 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 10.2)

08:05:23,533 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/135.155.175.224:8080

08:05:23,557 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) JBWEB003000: Coyote HTTP/1.1 starting on: http-/135.155.175.224:8080

08:05:23,799 INFO [org.jboss.ws.common.management] (MSC service thread 1-22) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3

08:05:23,932 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

08:05:23,933 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/UPMS]

08:05:23,954 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-26) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/opt/was/jboss/jboss-eap-6.3/standalone/deployments

08:05:23,976 INFO [org.jboss.as.remoting] (MSC service thread 1-32) JBAS017100: Listening on 135.155.175.224:4447

08:05:23,976 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 135.155.175.224:9999

08:05:24,210 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://135.155.175.224:9990/management

08:05:24,212 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://135.155.175.224:9990

08:05:24,212 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 6752ms - Started 157 of 195 services (56 services are lazy, passive or on-demand)

08:09:59,468 INFO [org.jboss.as.server.deployment] (MSC service thread 1-21) JBAS015876: Starting deployment of "DIDEAR.ear" (runtime-name: "DIDEAR.ear")

08:10:00,478 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015876: Starting deployment of "null" (runtime-name: "DIDWeb.war")

08:10:00,478 INFO [org.jboss.as.server.deployment] (MSC service thread 1-26) JBAS015876: Starting deployment of "null" (runtime-name: "DIDEJB.jar")

08:10:02,031 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry commons-beanutils.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/struts-1.2.8.jar does not point to a valid jar for a Class-Path reference.

08:10:02,033 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry commons-digester.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/struts-1.2.8.jar does not point to a valid jar for a Class-Path reference.

08:10:02,034 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry commons-fileupload.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/struts-1.2.8.jar does not point to a valid jar for a Class-Path reference.

08:10:02,035 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry commons-logging.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/struts-1.2.8.jar does not point to a valid jar for a Class-Path reference.

08:10:02,036 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry commons-validator.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/struts-1.2.8.jar does not point to a valid jar for a Class-Path reference.

08:10:02,037 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry jakarta-oro.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/struts-1.2.8.jar does not point to a valid jar for a Class-Path reference.

08:10:02,042 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry xercesImpl.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/xalan-2.5.1.jar does not point to a valid jar for a Class-Path reference.

08:10:02,043 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015960: Class Path entry xml-apis.jar in /content/DIDEAR.ear/DIDWeb.war/WEB-INF/lib/xalan-2.5.1.jar does not point to a valid jar for a Class-Path reference.

08:10:03,071 ERROR [org.jboss.as.jsf] (MSC service thread 1-22) JBAS012600: Could not load JSF managed bean class: org.apache.myfaces.tiles.example.TilesBacking

08:10:03,075 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-31) JNDI bindings for session bean named FindAvailDid in deployment unit subdeployment "DIDEJB.jar" of deployment "DIDEAR.ear" are as follows:

java:global/DIDEAR/DIDEJB/FindAvailDid!com.att.umdid.facade.findavaildid.FindAvailDidLocal

java:app/DIDEJB/FindAvailDid!com.att.umdid.facade.findavaildid.FindAvailDidLocal

java:module/FindAvailDid!com.att.umdid.facade.findavaildid.FindAvailDidLocal

java:global/DIDEAR/DIDEJB/FindAvailDid!com.att.umdid.facade.findavaildid.FindAvailDidLocalHome

java:app/DIDEJB/FindAvailDid!com.att.umdid.facade.findavaildid.FindAvailDidLocalHome

java:module/FindAvailDid!com.att.umdid.facade.findavaildid.FindAvailDidLocalHome

08:10:03,078 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-31) JNDI bindings for session bean named findExistingDid in deployment unit subdeployment "DIDEJB.jar" of deployment "DIDEAR.ear" are as follows:

java:global/DIDEAR/DIDEJB/findExistingDid!com.att.umdid.facade.findexistdid.findExistingDidLocal

java:app/DIDEJB/findExistingDid!com.att.umdid.facade.findexistdid.findExistingDidLocal

java:module/findExistingDid!com.att.umdid.facade.findexistdid.findExistingDidLocal

java:global/DIDEAR/DIDEJB/findExistingDid!com.att.umdid.facade.findexistdid.findExistingDidLocalHome

java:app/DIDEJB/findExistingDid!com.att.umdid.facade.findexistdid.findExistingDidLocalHome

java:module/findExistingDid!com.att.umdid.facade.findexistdid.findExistingDidLocalHome

08:10:03,079 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-31) JNDI bindings for session bean named EditRange in deployment unit subdeployment "DIDEJB.jar" of deployment "DIDEAR.ear" are as follows:

java:global/DIDEAR/DIDEJB/EditRange!com.att.umdid.facade.editRange.EditRangeLocal

java:app/DIDEJB/EditRange!com.att.umdid.facade.editRange.EditRangeLocal

java:module/EditRange!com.att.umdid.facade.editRange.EditRangeLocal

java:global/DIDEAR/DIDEJB/EditRange!com.att.umdid.facade.editRange.EditRangeLocalHome

java:app/DIDEJB/EditRange!com.att.umdid.facade.editRange.EditRangeLocalHome

java:module/EditRange!com.att.umdid.facade.editRange.EditRangeLocalHome

08:10:03,081 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-31) JNDI bindings for session bean named EditCntct in deployment unit subdeployment "DIDEJB.jar" of deployment "DIDEAR.ear" are as follows:

java:global/DIDEAR/DIDEJB/EditCntct!com.att.umdid.facade.editCntct.EditCntctLocal

java:app/DIDEJB/EditCntct!com.att.umdid.facade.editCntct.EditCntctLocal

java:module/EditCntct!com.att.umdid.facade.editCntct.EditCntctLocal

java:global/DIDEAR/DIDEJB/EditCntct!com.att.umdid.facade.editCntct.EditCntctLocalHome

java:app/DIDEJB/EditCntct!com.att.umdid.facade.editCntct.EditCntctLocalHome

java:module/EditCntct!com.att.umdid.facade.editCntct.EditCntctLocalHome

08:10:03,083 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-31) JNDI bindings for session bean named AddRange in deployment unit subdeployment "DIDEJB.jar" of deployment "DIDEAR.ear" are as follows:

java:global/DIDEAR/DIDEJB/AddRange!com.att.umdid.facade.addRange.AddRangeLocal

java:app/DIDEJB/AddRange!com.att.umdid.facade.addRange.AddRangeLocal

java:module/AddRange!com.att.umdid.facade.addRange.AddRangeLocal

java:global/DIDEAR/DIDEJB/AddRange!com.att.umdid.facade.addRange.AddRangeLocalHome

java:app/DIDEJB/AddRange!com.att.umdid.facade.addRange.AddRangeLocalHome

java:module/AddRange!com.att.umdid.facade.addRange.AddRangeLocalHome

08:10:03,084 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-31) JNDI bindings for session bean named TransHist in deployment unit subdeployment "DIDEJB.jar" of deployment "DIDEAR.ear" are as follows:

java:global/DIDEAR/DIDEJB/TransHist!com.att.umdid.facade.transhist.TransHistLocal

java:app/DIDEJB/TransHist!com.att.umdid.facade.transhist.TransHistLocal

java:module/TransHist!com.att.umdid.facade.transhist.TransHistLocal

java:global/DIDEAR/DIDEJB/TransHist!com.att.umdid.facade.transhist.TransHistLocalHome

java:app/DIDEJB/TransHist!com.att.umdid.facade.transhist.TransHistLocalHome

java:module/TransHist!com.att.umdid.facade.transhist.TransHistLocalHome

08:10:03,086 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-31) JNDI bindings for session bean named queryDid in deployment unit subdeployment "DIDEJB.jar" of deployment "DIDEAR.ear" are as follows:

java:global/DIDEAR/DIDEJB/queryDid!com.att.umdid.facade.querydid.queryDidLocal

java:app/DIDEJB/queryDid!com.att.umdid.facade.querydid.queryDidLocal

java:module/queryDid!com.att.umdid.facade.querydid.queryDidLocal

java:global/DIDEAR/DIDEJB/queryDid!com.att.umdid.facade.querydid.queryDidLocalHome

java:app/DIDEJB/queryDid!com.att.umdid.facade.querydid.queryDidLocalHome

java:module/queryDid!com.att.umdid.facade.querydid.queryDidLocalHome

08:10:03,419 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-22) MSC000001: Failed to start service jboss.deployment.subunit."DIDEAR.ear"."DIDWeb.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."DIDEAR.ear"."DIDWeb.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "DIDWeb.war" of deployment "DIDEAR.ear"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

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

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

at java.lang.Thread.run(Thread.java:682) [rt.jar:1.6.0_101]

Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information for class com.att.umdid.jsf.util.MainServlet with ClassLoader ModuleClassLoader for Module "deployment.DIDEAR.ear.DIDWeb.war:main" from Service Module Loader

at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:72) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)

at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:107)

at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:92)

at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:77)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

... 5 more

Caused by: java.lang.NoClassDefFoundError: beans/ProfileController

at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.6.0_101]

at java.lang.Class.privateGetDeclaredFields(Class.java:2412) [rt.jar:1.6.0_101]

at java.lang.Class.getDeclaredFields(Class.java:1783) [rt.jar:1.6.0_101]

at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:68) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

... 10 more

Caused by: java.lang.ClassNotFoundException: beans.ProfileController from [Module "deployment.DIDEAR.ear.DIDWeb.war:main" from Service Module Loader]

at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1]

at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1]

at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:447) [jboss-modules.jar:1.3.3.Final-redhat-1]

at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:414) [jboss-modules.jar:1.3.3.Final-redhat-1]

at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final-redhat-1]

at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final-redhat-1]

... 15 more

08:10:03,452 ERROR [org.jboss.as.server] (HttpManagementService-threads - 3) JBAS015870: Deploy of deployment "DIDEAR.ear" was rolled back with the following failure message:

{

"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"DIDEAR.ear\".\"DIDWeb.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"DIDEAR.ear\".\"DIDWeb.war\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"DIDWeb.war\" of deployment \"DIDEAR.ear\"

Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information for class com.att.umdid.jsf.util.MainServlet with ClassLoader ModuleClassLoader for Module \"deployment.DIDEAR.ear.DIDWeb.war:main\" from Service Module Loader

Caused by: java.lang.NoClassDefFoundError: beans/ProfileController

Caused by: java.lang.ClassNotFoundException: beans.ProfileController from [Module \"deployment.DIDEAR.ear.DIDWeb.war:main\" from Service Module Loader]"},

"JBAS014771: Services with missing/unavailable dependencies" => [

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.findExistingDid.Validator is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.findExistingDid]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditCntct.ValidatorFactory is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditCntct]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.TransHist.Validator is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.TransHist]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.TransHist.ValidatorFactory is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.TransHist]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditRange.ValidatorFactory is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditRange]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.queryDid.ValidatorFactory is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.queryDid]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditRange.Validator is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditRange]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditCntct.Validator is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditCntct]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.FindAvailDid.Validator is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.FindAvailDid]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.AddRange.ValidatorFactory is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.AddRange]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.AddRange.Validator is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.AddRange]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.FindAvailDid.ValidatorFactory is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.FindAvailDid]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.queryDid.Validator is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.queryDid]",

"jboss.naming.context.java.comp.DIDEAR.DIDEJB.findExistingDid.ValidatorFactory is missing [jboss.naming.context.java.comp.DIDEAR.DIDEJB.findExistingDid]"

]

}

08:10:03,514 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015877: Stopped deployment null (runtime-name: DIDEJB.jar) in 62ms

08:10:03,655 INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015877: Stopped deployment null (runtime-name: DIDWeb.war) in 203ms

08:10:03,669 INFO [org.jboss.as.server.deployment] (MSC service thread 1-24) JBAS015877: Stopped deployment DIDEAR.ear (runtime-name: DIDEAR.ear) in 221ms

08:10:03,675 INFO [org.jboss.as.controller] (HttpManagementService-threads - 3) JBAS014774: Service status report

JBAS014775: New missing/unsatisfied dependencies:

service jboss.naming.context.java.comp.DIDEAR.DIDEJB.AddRange (missing) dependents: [service jboss.naming.context.java.comp.DIDEAR.DIDEJB.AddRange.ValidatorFactory, service jboss.naming.context.java.comp.DIDEAR.DIDEJB.AddRange.Validator]

service jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditCntct (missing) dependents: [service jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditCntct.ValidatorFactory, service jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditCntct.Validator]

service jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditRange (missing) dependents: [service jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditRange.ValidatorFactory, service jboss.naming.context.java.comp.DIDEAR.DIDEJB.EditRange.Validator]

service jboss.naming.context.java.comp.DIDEAR.DIDEJB.FindAvailDid (missing) dependents: [service jboss.naming.context.java.comp.DIDEAR.DIDEJB.FindAvailDid.ValidatorFactory, service jboss.naming.context.java.comp.DIDEAR.DIDEJB.FindAvailDid.Validator]

service jboss.naming.context.java.comp.DIDEAR.DIDEJB.TransHist (missing) dependents: [service jboss.naming.context.java.comp.DIDEAR.DIDEJB.TransHist.ValidatorFactory, service jboss.naming.context.java.comp.DIDEAR.DIDEJB.TransHist.Validator]

service jboss.naming.context.java.comp.DIDEAR.DIDEJB.findExistingDid (missing) dependents: [service jboss.naming.context.java.comp.DIDEAR.DIDEJB.findExistingDid.Validator, service jboss.naming.context.java.comp.DIDEAR.DIDEJB.findExistingDid.ValidatorFactory]

service jboss.naming.context.java.comp.DIDEAR.DIDEJB.queryDid (missing) dependents: [service jboss.naming.context.java.comp.DIDEAR.DIDEJB.queryDid.Validator, service jboss.naming.context.java.comp.DIDEAR.DIDEJB.queryDid.ValidatorFactory]

service jboss.naming.context.java.module.DIDEAR.DIDEJB (missing) dependents: [service jboss.deployment.subunit."DIDEAR.ear"."DIDEJB.jar".INSTALL]

JBAS014777: Services which failed to start: service jboss.deployment.subunit."DIDEAR.ear"."DIDWeb.war".POST_MODULE

1. Re: Unable to deploy EAR on JBOSS EAP 6.3

jaysensharma Nov 19, 2015 12:14 PM (in response to abhi415)
The error indicates that the class "beans.ProfileController" is not being found.

java.lang.RuntimeException: JBAS018757: Error getting reflective information for class com.att.umdid.jsf.util.MainServlet with ClassLoader ModuleClassLoader for Module "deployment.DIDEAR.ear.DIDWeb.war:main" from Service Module Loader . . Caused by: java.lang.NoClassDefFoundError: beans/ProfileController Caused by: java.lang.ClassNotFoundException: beans.ProfileController from [Module \"deployment.DIDEAR.ear.DIDWeb.war:main\" from Service Module Loader]"},

Can you please let us know where exactly you have placed this class "beans.ProfileController" inside "DIDWeb.war/WEB-INF/classes" OR inside some JAR present inside the "DIDWeb.war/WEB-INF/lib" or inside some jar present inside "DIDEAR.ear/lib" Or you are putting that class in some JBoss custom module ?
Actions
2. Re: Unable to deploy EAR on JBOSS EAP 6.3

abhi415 Nov 20, 2015 4:33 AM (in response to jaysensharma)

Thanks much Jay for your reply. I'm actually new to this project. But just now I got to know that this project has dependency on other project. I have deployed the EAR of the other project as well. But now when I've deployed the EAR for other project, I'm getting blank page when hitting application URL.

Am I missing something here? Do I have to make entry of context-root to any other place as well apart from application.xml?

and that beans.ProfileController resides in UPMSSO.war.
Could you please provide your valuable suggestions?
Actions
3. Re: Unable to deploy EAR on JBOSS EAP 6.3

jaysensharma Nov 20, 2015 6:37 AM (in response to abhi415)
As your application "DIDEAR.ear/DIDWeb.war" needs access to the class "beans.ProfileController" which is present inside the other EAR "UPMSSSO.ear/UPMSSO.war" hence you may need to use the "DIDEAR.ear/META-INF/jboss-deployment-structure.xml" file something like following to tell JBoss to make the class available for the DIDEAR.ear which is present in another deployment "UPMSSSO.ear/UPMSSO.war":

Add the following entry: "DIDEAR.ear/META-INF/jboss-deployment-structure.xml"

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment> <dependencies> <module name="deployment.UPMSSSO.ear.UPMSSO.war" export="true"/>  </dependencies> </deployment> </jboss-deployment-structure>

If you still get blank page then please share the complete log during the deployment and let us know which kind of page are you accessing (a servlet/JSP/JSF component ...etc)
Actions
4. Re: Unable to deploy EAR on JBOSS EAP 6.3

abhi415 Nov 20, 2015 7:02 AM (in response to jaysensharma)
Thanks again for your time. But I have two points:

These projects are running fine in websphere.
I don't have "DIDEAR.ear/META-INF/jboss-deployment-structure.xml" file in my project so shall I have to create this file?
Actions
5. Re: Unable to deploy EAR on JBOSS EAP 6.3

jaysensharma Nov 20, 2015 7:15 AM (in response to abhi415)

WebSphere classloading mechanism is not exactly same as JBossAS7 (EAP6) modularized classloading.
So try creating that file and DIDEAR.ear/META-INF/jboss-deployment-structure.xml and then see if it fixes at least the ClassNotFoundException: beans.ProfileController.

Also please see the following link in order to know more about JBossAS7/EAP6 classloading:
https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7
https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/chap-Class_Loading_and_Modules.html
Actions

Go to original post