ServiceNotFoundException: 未找到服务 service jboss.ejb.default-resource-adapter-name-service。

huangapple go评论42阅读模式
英文:

org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found

问题

抱歉,我无法提供对代码的实时翻译。如果您有任何与上述代码相关的问题或需求,请随时告诉我,我将尽力为您提供帮助。

英文:

I have created enterprise project in eclipse . dynamic web project and ejb project has reference for enterprise project.
When i running admin(enterprise project) run as selecting wildfly server 18.I am getting below error.
Can anyone tell what i am missing .

20:09:48,376 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."Admin.ear"."Admin-web.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."Admin.ear"."Admin-web.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "Admin-web.war" of deployment "Admin.ear"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
	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:1982)
	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:745)
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:663)
	at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:248)
	at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:156)
	at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:83)
	at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:50)
	at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)

答案1

得分: 7

I found that I was not setting the resource-adapter-name. I resolved this by updating my standalone.xml and adding the below <mdb> element inside <subsystem xmlns="urn:jboss:domain:ejb3:6.0">

<mdb>
    <resource-adapter-ref resource-adapter-name="${ejb.resource-adapter-name:hornetq.rar}"/>
    <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
</mdb>

In my case the resource-adapter-name is hornetq.rar

英文:

I found that I was not setting the resource-adapter-name. I resolved this by updating my standalone.xml and adding the below &lt;mdb&gt; element inside &lt;subsystem xmlns=&quot;urn:jboss:domain:ejb3:6.0&quot;&gt;

&lt;mdb&gt;
    &lt;resource-adapter-ref resource-adapter-name=&quot;${ejb.resource-adapter-name:hornetq.rar}&quot;/&gt;
    &lt;bean-instance-pool-ref pool-name=&quot;mdb-strict-max-pool&quot;/&gt;
&lt;/mdb&gt;

In my case the resource-adapter-name is hornetq.rar

huangapple
  • 本文由 发表于 2020年7月31日 00:24:27
  • 转载请务必保留本文链接:https://go.coder-hub.com/63177386.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定