Hi, Kie server relies usually on JMS message subsystem. In this case seems to me that that extension on EPA is not active. Either you have a bad installation or you are running this incorrectly through command line. You have 2 options.
Add the jms extension yourself (a bit complex) as you need to configure other subystems.
run the wildfly through command line
./standalone.sh -c standalone-full.xml
standalone-full.xml is the jboss configuration containing already the configuration for jms / messaging.
------------------------------
Enrique González Martínez
------------------------------
Original Message:
Sent: Fri July 28, 2023 06:10 AM
From: Kishan Kumar
Subject: Can not deploy KIE server because of service jboss.ejb.default-resource-adapter-name-service not found
Hi Everyone,
I am trying to deploy the KIE server but getting an error service not found.
12:06:46,862 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kie-server.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "kie-server.war"
at org.jboss.as.server@15.0.2.Final-redhat-00001//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc@1.4.12.Final-redhat-00001//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc@1.4.12.Final-redhat-00001//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc@1.4.12.Final-redhat-00001//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final-redhat-00001//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.jboss.msc.service.ServiceNotFoundException: service jboss.ejb.default-resource-adapter-name-service not found
at org.jboss.msc@1.4.12.Final-redhat-00001//org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
at org.jboss.as.ejb3@7.4.0.GA-redhat-00005//org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:263)
at org.jboss.as.ejb3@7.4.0.GA-redhat-00005//org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:156)
at org.jboss.as.ejb3@7.4.0.GA-redhat-00005//org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:83)
at org.jboss.as.ejb3@7.4.0.GA-redhat-00005//org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:150)
at org.jboss.as.ejb3@7.4.0.GA-redhat-00005//org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.deploy(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:82)
at org.jboss.as.server@15.0.2.Final-redhat-00001//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
------------------------------
Kishan Kumar
------------------------------