'Deployment of process archive 'null': Cannot deploy process archive 'null' to default process: no such process engine exists: processEngine is null


#1

I was getting below error when i start my springboot application.

[15-May-2018 11:43:30.030] [main] INFO org.camunda.bpm.container.logInfo:128 - ENGINE-08024 Found processes.xml file at file:/C:/sts-3.9.1-workspace/operativeworkflow/bin/main/META-INF/processes.xml
[15-May-2018 11:43:30.086] [main] INFO org.apache.catalina.core.StandardService.log:180 - Stopping service [Tomcat]
[15-May-2018 11:43:30.107] [main] ERROR org.springframework.boot.SpringApplication.reportFailure:842 - Application run failed
java.lang.RuntimeException: org.camunda.bpm.engine.ProcessEngineException: ENGINE-08043 Exception while performing ‘Deployment of Process Application workflowApplication’ => 'Deployment of process archive ‘null’: Cannot deploy process archive ‘null’ to default process: no such process engine exists: processEngine is null
at org.camunda.bpm.engine.spring.application.SpringProcessApplication.onApplicationEvent(SpringProcessApplication.java:99)
at org.camunda.bpm.engine.spring.application.SpringProcessApplication.onApplicationEvent(SpringProcessApplication.java:48)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:354)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:888)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:161)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:395)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:327)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1255)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1243)
at com.operative.workflow.WorkflowApplication.main(WorkflowApplication.java:25)
Caused by: org.camunda.bpm.engine.ProcessEngineException: ENGINE-08043 Exception while performing ‘Deployment of Process Application workflowApplication’ => 'Deployment of process archive ‘null’: Cannot deploy process archive ‘null’ to default process: no such process engine exists: processEngine is null
at org.camunda.bpm.container.impl.ContainerIntegrationLogger.exceptionWhilePerformingOperationStep(ContainerIntegrationLogger.java:312)
at org.camunda.bpm.container.impl.spi.DeploymentOperation.execute(DeploymentOperation.java:132)
at org.camunda.bpm.container.impl.jmx.MBeanServiceContainer.executeDeploymentOperation(MBeanServiceContainer.java:156)
at org.camunda.bpm.container.impl.spi.DeploymentOperation$DeploymentOperationBuilder.execute(DeploymentOperation.java:212)
at org.camunda.bpm.container.impl.RuntimeContainerDelegateImpl.deployProcessApplication(RuntimeContainerDelegateImpl.java:95)
at org.camunda.bpm.application.AbstractProcessApplication.deploy(AbstractProcessApplication.java:59)
at org.camunda.bpm.engine.spring.application.SpringProcessApplication.start(SpringProcessApplication.java:104)
at org.camunda.bpm.engine.spring.application.SpringProcessApplication.afterPropertiesSet(SpringProcessApplication.java:113)
at org.camunda.bpm.spring.boot.starter.SpringBootProcessApplication.afterPropertiesSet(SpringBootProcessApplication.java:74)
at org.camunda.bpm.engine.spring.application.SpringProcessApplication.onApplicationEvent(SpringProcessApplication.java:90)
… 16 common frames omitted
Caused by: org.camunda.bpm.engine.exception.NullValueException: Cannot deploy process archive ‘null’ to default process: no such process engine exists: processEngine is null
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.camunda.bpm.engine.impl.util.EnsureUtil.generateException(EnsureUtil.java:344)
at org.camunda.bpm.engine.impl.util.EnsureUtil.ensureNotNull(EnsureUtil.java:49)
at org.camunda.bpm.engine.impl.util.EnsureUtil.ensureNotNull(EnsureUtil.java:44)
at org.camunda.bpm.container.impl.deployment.DeployProcessArchiveStep.getProcessEngine(DeployProcessArchiveStep.java:214)
at org.camunda.bpm.container.impl.deployment.DeployProcessArchiveStep.performOperationStep(DeployProcessArchiveStep.java:78)
at org.camunda.bpm.container.impl.spi.DeploymentOperation.execute(DeploymentOperation.java:116)
… 24 common frames omitted
[15-May-2018 11:43:30.111] [main] WARN org.camunda.bpm.application.logWarn:142 - ENGINE-07017 Calling undeploy() on process application that is not deployed.


#2

I have the same issue. For my setup the error is only occuring, when I try to change the engine name via Spring Boot application.properties using the camunda.bpm.process-engine-name=example. I have described the situation in detail in this stackoverflow-ticket https://stackoverflow.com/questions/54142174


#3

I have resolved the issue longback


#4

Hi, sorry I’m not sure what you mean by that answer? Have you solved the issue in your configuration? Could you share your solution?


#5

Its related to process engine configuration, we created custom process engine through configurations. We done this, just for testing process. Now we are using default process engine only.