I am starting to start Wildfly AS 8.2.0 on a Windows 7 32 bit machine but get the following error:
19:59:01,582 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.remoting.endpoint.management: org.jboss.msc.service.StartException in service jboss.remoting.endpoint.management: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67]
Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found
at org.xnio.Xnio.doGetInstance(Xnio.java:238)
at org.xnio.Xnio.getInstance(Xnio.java:193)
at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112)
at org.jboss.as.remoting.ManagementEndpointService.createEndpoint(ManagementEndpointService.java:45)
at org.jboss.as.remoting.EndpointService.start(EndpointService.java:76)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
... 3 more
I think its one of the xnio libraries missing. (I would have commented your post if I could, I just do not have enough reputation to do so.) Make sure to have everything needed in the classpath.
EDIT: Yes, thats the problem. Theres no XNIO provider in the cp
Related
a strange thing is going on and I need you help to point me into the correct direction.
After the upgrade from WildFly15 to WildFly 24.0.1 some (not all) applications fail during deployment with the following warnings and error(s):
2021-08-12 14:33:59,148 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0003: Could not index class org/osgi/service/device/Match.class at /content/myapplication.war/WEB-INF/lib/org.eclipse.osgi.services-3.3.100.v20130513-1956.jar: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:317)
at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:259)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:318)
at java.util.jar.JarVerifier.update(JarVerifier.java:230)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:455)
at org.jboss.vfs.spi.JavaZipFileSystem.openInputStream(JavaZipFileSystem.java:182)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:318)
at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:98)
at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
2021-08-12 14:34:01,181 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."myapplication.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."myapplication.war".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "myapplication.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:317)
at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:259)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:318)
at java.util.jar.JarVerifier.update(JarVerifier.java:230)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:455)
at org.jboss.vfs.spi.JavaZipFileSystem.openInputStream(JavaZipFileSystem.java:182)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:318)
at org.jboss.vfs.VFSUtils.readManifest(VFSUtils.java:241)
at org.jboss.vfs.VFSUtils.getManifest(VFSUtils.java:227)
at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.getManifest(ManifestAttachmentProcessor.java:76)
at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:65)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
WildFly has the same configuration, its on the same machine and we use the same JVM (1.8.something) to run the server.
The error is caused by one or more invalid signatures in the jars in /WEB-INF/lib
Why does it appear now on the new server (wasnt WF15 validating the
jars already)?
How to solve?
Can we remove signatures from the jars during war assemply using maven or disable signature check on WF24?
Any help/hint is highly appreciated!
Have a nice day!
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
I am trying to start up wildfly-8.2 standalone , i am getting an exception . Please check exception log below.
C:\jboss\wildfly-8.2.0.Final\bin>standalone.bat
Calling "C:\jboss\wildfly-8.2.0.Final\bin\standalone.conf.bat"
Setting JAVA property to "C:\Program Files\Java\jdk1.7.0_79\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\jboss\wildfly-8.2.0.Final"
JAVA: "C:\Program Files\Java\jdk1.7.0_79\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"
===============================================================================
12:53:13,775 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
12:53:14,138 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
12:53:14,221 INFO [org.jboss.as] (MSC service thread 1-8) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
12:53:14,767 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014
676: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:259) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: javax.xml.stream.XMLStreamException: JBAS014674: Failed to load module org.jboss.as.cmp
at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:155) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:325) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:137) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
... 3 more
Caused by: java.util.concurrent.ExecutionException: java.lang.UnsupportedOperationException: JBAS013452: Legacy extension 'org.jboss.as.cmp' is not supported on servers running this vers
ion. The extension is only supported for use by hosts running a previous release in a mixed-version managed domain
at java.util.concurrent.FutureTask.report(FutureTask.java:122) [rt.jar:1.7.0_79]
at java.util.concurrent.FutureTask.get(FutureTask.java:188) [rt.jar:1.7.0_79]
at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:147) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
... 9 more
Caused by: java.lang.UnsupportedOperationException: JBAS013452: Legacy extension 'org.jboss.as.cmp' is not supported on servers running this version. The extension is only supported for
use by hosts running a previous release in a mixed-version managed domain
at org.jboss.as.controller.extension.AbstractLegacyExtension.initializeParsers(AbstractLegacyExtension.java:82) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:183) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:69) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:127) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:124) [wildfly-controller-8.2.0.Final.jar:8.2.0.Final]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
12:53:15,101 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
12:53:15,136 INFO [org.jboss.as] (MSC service thread 1-8) JBAS015950: WildFly 8.2.0.Final "Tweek" stopped in 16ms
Thank you. Apparently i was using standalone.xml from jboss 7.1.1 which does not work. I replaced it with default standalone.xml which worked fine.
I don't know how, but it looks like you managed to get the 'org.jboss.as.cmp' extension into the configuration file. Try looking into standalone.xml and find this: <extension module="org.jboss.as.cmp"/> and remove it.
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
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.