StartException in service persistenceunit - possible issue Hibernate queries? - java

I have a Liferay portlet project that I'd like to deploy on JBoss + Liferay. This worked fine earlier but other project that this depends on changed over time. When I try to deploy my portlet, I get the following exception
09:07:40,261 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-7) HHH000397: Using ASTQueryTranslatorFactory
09:07:40,608 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-7) Hibernate Validator 4.2.0.Final
09:07:43,046 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.persistenceunit."biz.modit.tit.gop.education.clientportlets.adaptivetest-0.0.1-SNAPSHOT.war#GOPPersistence": org.jboss.msc.service.StartException in service jboss.persistenceunit."biz.modit.tit.gop.education.clientportlets.adaptivetest-0.0.1-SNAPSHOT.war#GOPPersistence": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.NullPointerException
at org.hibernate.loader.BasicLoader.isBag(BasicLoader.java:98)
at org.hibernate.loader.BasicLoader.postInstantiate(BasicLoader.java:77)
at org.hibernate.loader.hql.QueryLoader.<init>(QueryLoader.java:120)
at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:204)
at org.hibernate.hql.internal.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136)
at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:101)
at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:80)
at org.hibernate.engine.query.spi.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:119)
at org.hibernate.internal.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:974)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:485)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:84)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
Based on this I suspect that there's a problem with one of the queries in the entity project (containing all the jpa entities and named queries, etc). So is there a tool for checking the correctness of the hql queries? Or do you have any other suspicion regarding what could cause the problem?
The above exception is the only exception I get regarding the issue.

Related

jboss Services which failed to start

During deployment to jbosss 7.2.final, the ear project received the following error exception:
JBAS014777: Services which failed to start: service
jboss.persistenceunit."Morfeusflex-ear-1.0.ear/Morfeusflex-
ejb-1.0.jar#MorfeusflexPU": org.jboss.msc.service.StartException in
service jboss.persistenceunit."Morfeusflex-ear-1.0.ear/Morfeusflex-
ejb-1.0.jar#MorfeusflexPU": java.lang.AbstractMethodError
This error happened when I upgraded hibernate 3 to hibernate 5 in the pom.xml file.
All Exceptions from log file
16:14:30,049 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 312) MSC00001: Failed to start service jboss.persistenceunit."Morfeusflex-ear-1.0.ear/Morfeusflex-ejb-1.0.jar#MorfeusflexPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."Morfeusflex-ear-1.0.ear/Morfeusflex-ejb-1.0.jar#MorfeusflexPU": java.lang.AbstractMethodError
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_76]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_76]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_76]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.AbstractMethodError
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:303)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1742)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99)
... 4 more
16:14:30,055 FINE [javax.xml.bind] (MSC service thread 1-7) Trying to locate morfeusflex/service/billingaddress/jaxws_asm/jaxb.properties
16:14:30,056 FINE [javax.xml.bind] (MSC service thread 1-7) not found
16:14:30,435 FINE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 309) javax.naming.NameNotFoundException: env/ClientStateSavingPassword -- service jboss.naming.context.java.module."Morfeusflex-ear-1.0"."Morfeusflex-web-1.0".env.ClientStateSavingPassword
16:14:30,435 FINE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 309) javax.naming.NameNotFoundException: env/jsf/ProjectStage -- service jboss.naming.context.java.module."Morfeusflex-ear-1.0"."Morfeusflex-web-1.0".env.jsf.ProjectStage
{"JBAS014671: Failed services" => {"jboss.persistenceunit.\"Morfeusflex-ear-1.0.ear/Morfeusflex-ejb-1.0.jar#MorfeusflexPU\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"Morfeusflex-ear-1.0.ear/Morfeusflex-ejb-1.0.jar#MorfeusflexPU\": java.lang.AbstractMethodError
16:14:31,954 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 313) MSC00001: Failed to start service jboss.persistenceunit."Morfeusflex-ear-1.0.ear/Morfeusflex-ejb-1.0.jar#MorfeusflexPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."Morfeusflex-ear-1.0.ear/Morfeusflex-ejb-1.0.jar#MorfeusflexPU": java.lang.AbstractMethodError
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_76]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_76]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_76]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.AbstractMethodError
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:303)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1742)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99)
... 4 more
16:14:32,507 FINE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 308) javax.naming.NameNotFoundException: env/ClientStateSavingPassword -- service jboss.naming.context.java.module."Morfeusflex-ear-1.0"."Morfeusflex-web-1.0".env.ClientStateSavingPassword
16:14:32,507 FINE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 308) javax.naming.NameNotFoundException: env/jsf/ProjectStage -- service jboss.naming.context.java.module."Morfeusflex-ear-1.0"."Morfeusflex-web-1.0".env.jsf.ProjectStage
Please have a look and provide me solution

Error when deploying PersistenceUnit: IllegalArgumentException expecting collection type [boolean]

Since a week I'm getting this error when deploying my ear to JBoss EAP 6.2.0
19:48:56,355 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 79) MSC000001: Failed to start service jboss.persistenceunit."Weare-0.1-dev.ear/WeAreEjb.jar#weareUnit": org.jboss.msc.service.StartException in service jboss.persistenceunit."Weare-0.1-dev.ear/WeAreEjb.jar#weareUnit": java.lang.IllegalArgumentException: Expecting collection type [boolean]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
**Caused by: java.lang.IllegalArgumentException: Expecting collection type [boolean]**
at org.hibernate.ejb.metamodel.AttributeFactory.determineCollectionType(AttributeFactory.java:902)
at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:756)
at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:737)
at org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:520)
at org.hibernate.ejb.metamodel.AttributeFactory.buildAttribute(AttributeFactory.java:100)
at org.hibernate.ejb.metamodel.MetadataContext.wrapUp(MetadataContext.java:207)
at org.hibernate.ejb.metamodel.MetamodelImpl.buildMetamodel(MetamodelImpl.java:83)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:106)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:76)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
... 4 more
I've logged these classes:
org.hibernate
org.jboss.jpa
org.jboss.service.msc
Initially with log level ERROR, then TRACE, ending with ALL, but there is no trace of this error in log files...can anyone tell me which other classes are useful for logging this exception?
I believed that org.hibernate was sufficient, because the exception is thrown by an hibernate class...

OSGi bundle with other OSGi bundle as dependencies

I have a project where it has many OSGI bundles with one web (.war). Some OSGi have other OSGi as dependencies and war uses all OSGi as dependencies.
Problem. When I redeploy one of the OSGi bundles then dependent OSGi gets stopped, also war gets unregistered. Is there any way that after redeploy, dependent OSGi and war get refreshed (redeploy) automatically? I am using JBOSS EAP 7.3.0 application server.
Exception is :
11:01:14,238 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."W.war".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."W.war".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "W.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
Caused by: java.lang.NullPointerException
at org.jboss.as.jpa.processor.JPAInterceptorProcessor.deploy(JPAInterceptorProcessor.java:52)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
... 5 more

How to ignore WebService error in JBoss EAP 6?

I have to make a compatible .ear for WebSphere 6.1 (which is only JAX-RPC/Java1.5) and JBoss EAP 6 (JAX-WS/Java7). There is a webservice in WebSphere 6.1 that works with JAX-RPC and i want to create the exact same webservice in JBoss using JAX-WS. But my problem is that once JBoss encountered a error in the JAX-RPC service it stops from deploying the rest of the application. Is there a way to make JBoss ignore the JAX-RPC service and only initialize JAX-WS ? Or is it possible to completely deactivate JAX-RPC with deployment.xml?
Regards
Edit :
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.subunit."YYY.ear"."waYYY.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."YYY.ear"."waYYY.war".INSTALL: JBAS018733: N'a pas pu traiter la phase INSTALL de subdeployment "waYYY.war" of deployment "YYY.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
Caused by: org.jboss.ws.WSException: JBWS025146: Cannot obtain java type mapping for: {urn:YYYEventWS/types}doConsume
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.processDocElement(JAXRPCMetaDataBuilder.java:583)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildParameterMetaDataDoc(JAXRPCMetaDataBuilder.java:840)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.setupOperationsFromWSDL(JAXRPCMetaDataBuilder.java:202)
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buildMetaData(JAXRPCServerMetaDataBuilder.java:197)
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:58)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
... 5 more

Jboss server error : Failed to start service jboss.deployment.unit."jbpm-console.war"

When starting the jboss server, it giving an error Failed to start service jboss.deployment.unit."jbpm-console.war". But when i'm running jbpm6 demo using start.demo its working fine.
23:43:41,042 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."jbpm-console.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbpm-console.war".PARSE: Failed to process phase PARSE of deployment "jbpm-console.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:273)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageDrivenBeanMetaData(MessageDrivenComponentDescriptionFactory.java:244)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processBeanMetaData(MessageDrivenComponentDescriptionFactory.java:88)
at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processBeanMetaData(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:65)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.processDeploymentDescriptor(AbstractDeploymentUnitProcessor.java:143)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:84)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
23:43:41,104 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015951: Admin console listening on http://127.0.0.1:9990
23:43:41,104 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jbpm-console.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jbpm-console.war\".PARSE: Failed to process phase PARSE of deployment \"jbpm-console.war\""}}
23:43:41,104 ERROR [org.jboss.as] (MSC service thread 1-6) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 49681ms - Started 344 of 423 services (1 services failed or missing dependencies, 76 services are passive or on-demand)
23:43:41,104 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "dashboard-builder.war" was rolled back with no failure message

try staring jboss with ./standalone.sh -c standalone-full.xml or any other alternative that allows you to start with the full profile

Best solution: Goto jboss-as-7.1.1.Final\standalone\deployments folder and delete all existing files....
Run again your problem will be solved

I had the exact same problem, found that I was missing
<mdb>
<resource-adapter-ref resource-adapter-name="hornetq-ra"/>
<bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
</mdb>
under
<subsystem xmlns="urn:jboss:domain:ejb3:1.2">
in standalone/configuration/standalone.xml

delete your project folder under C:\....\wildfly-9.0.1.Final\standalone\deployments\YOUR-PROJEKT-FOLDER
restart your wildfly-server

you should run standlone.bat or .sh with -c standalone-full.xml switch
may be work.

I had a similar issue, my error was:
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException:org.glassfish.jersey.servlet.ServletContainer from [Module "deployment.RESTful_Services_CRUD.war:main" from Service Module Loader]
I use jboss and glassfish so I changed the web.xml to the following:
<servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
Instead of:
<servlet-class>org.glassfish.jersey.servlet.ServletContainer</servlet-class>
Hope this work for you.

If you use Intellij Idea you can click services tab and select artifacts. Then you can click add all and ok.

Categories