Service org.camunda.bpm.platform.process-engine.default is already registered

Camunda 7 Topics Discussion & Questions
1

Hi Camunda Team,

i have configurated my process-engine in my processes.xml and by starting my application i got the error “Service org.camunda.bpm.platform.process-engine.default is already registered”. I understood the error but don’t know why.

My processes.xml looks like so:

<process-engine name="default">
    <job-acquisition>default</job-acquisition>
    <datasource>java:jboss/datasources/ProcessEngine</datasource>

    <properties>
        <property name="jobExecutorActivate">false</property>
        <property name="customPostBPMNParseListeners">
            org.camunda.bpm.engine.impl.bpmn.parser.FoxFailedJobParseListener
        </property>
        <property name="foxFailedJobCommandFactory">
            org.camunda.bpm.engine.impl.jobexecutor.FoxFailedJobCommandFactory
        </property>
    </properties>

    <plugins>
        <plugin>
            <class>xxxx/myProcessEnginePlugin</class>
        </plugin>
    </plugins>
</process-engine>
default false true

The Error log:

2017-05-15 08:33:31,866 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.“myApplication.war”.INSTALL: org.jboss.
msc.service.StartException in service jboss.deployment.unit.“myApplication.war”.INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment “myApplication.war”
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.DuplicateServiceException: Service org.camunda.bpm.platform.process-engine.default is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
at org.camunda.bpm.container.impl.jboss.deployment.processor.ProcessEngineStartProcessor.startProcessEngine(ProcessEngineStartProcessor.java:93)
at org.camunda.bpm.container.impl.jboss.deployment.processor.ProcessEngineStartProcessor.deploy(ProcessEngineStartProcessor.java:58)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
… 5 more

Thanks for any help!
Regards
Fan

2

Hi Fan,

Are you running the JBoss distribution that can be downloaded from camunda.org?

Cheers,
Thorben

3

Hi Thorben,

i am running the newest wildfly downloaded from camunda.org.

Regards
Fan

4

Did you disable the default engine configured in standalone.xml? This Wildfly distribution comes with a preconfigured engine named default, so you’ll have to disable it before your application starts another engine with that name.

5

Hi Thorben,

thanks for reply. I have deleted the default engine configuration in standalone.xml but there are still Errors and the Deployment was also unsuccessful.

2017-05-15 13:15:25,005 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation (“full-replace-deployment”) failed - address: ([]) - failu
re description: {
“WFLYCTL0412: Required services that are not installed:” => [
“org.camunda.bpm.platform.process-engine.default”,
“jboss.naming.context.java.global.camunda-bpm-platform.process-engine.default”
],
“WFLYCTL0180: Services with missing/unavailable dependencies” => [
“org.camunda.bpm.platform.process-application-module.“deployment.myApp.war:main”.START is missing [org.camunda.bpm.platform.process-engine.default]”,
“jboss.naming.context.java.module.myApp.myApp.env.“xxx.ProcessManagerBean”.processEngine is missing
[jboss.naming.context.java.global.camunda-bpm-platform.process-engine.default]”
]
}
2017-05-15 13:15:25,014 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint.“myApp.war”.EventServiceMock
2017-05-15 13:15:25,014 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint.“myApp.war”.RipsServiceMock
2017-05-15 13:15:25,075 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment myApp.war (runtime-name: myApp.war) in 67ms
2017-05-15 13:15:25,076 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0190: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@
52d1a58a for operation {“operation” => “full-replace-deployment”,“address” => [],“name” => “myApp.war”,“content” => [{“input-stream-index” => 0}],“enabled” => true,“operation-header
s” => {“caller-type” => “user”,“access-mechanism” => “NATIVE”},“runtime-name” => undefined,“persistent” => true,“owner” => undefined} at address [] failed handling operation rollback – java
.util.NoSuchElementException: No child ‘name’ exists: java.util.NoSuchElementException: No child ‘name’ exists
at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:377)
at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:299)
at org.jboss.dmr.ModelNode.require(ModelNode.java:870)
at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:277)
at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1384)
at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1366)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1311)
at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185)
at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:667)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:400)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:222)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)

Do you have any further suggestion?
Regards
Fan

6

Hi @thorben,

How can I disable the default engine configured in the standalone.xml without deleting the configuration for the standalone.xml? My use case is that the runtime is running in a docker container and I would like to overwrite the default config to the following:

image
image1037×685 25 KB

Thanks in advance