Deployment problem

Camunda 7 Topics Discussion & Questions
1

When I deploy, an error is reported as follows:
org.camunda.bpm.engine.context - ENGINE-16004 Exception while closing command context: The deployment contains definitions with the same key ‘’ (id attribute), this is not allowed

org.camunda.bpm.engine.ProcessEngineException: The deployment contains definitions with the same key ‘’ (id attribute), this is not allowed

at org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.ensureNoDuplicateDefinitionKeys(AbstractDefinitionDeployer.java:192)

at org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.deploy(AbstractDefinitionDeployer.java:65)

We look forward to your help. Thank you very much!

wisdom

2

Can you explain exactly what you’re deploying, how you’re doing the deployment and which distro you’re deploying to?

3

I am conducting secondary development based on camunda, and associating process files with form files during deployment. Camunda version is 7.16.0

4

Do all of the processes you’re deploying have the different process ids?

5

Yes.

image
image1607×903 54.1 KB

image
image1306×404 19.1 KB

Sorry,I can only show you this because I can’t upload files

6

Hello @wisdom ,

What does your processes.xml look like?

Jonathan

7

Check all your forms very carefully.
Several users have had issues where the contents of the form resulted in duplicate keys (they were null, so deploying each form individually would work, but two forms together would not)

1 Like
8

Cool!You are right.
After I redraw the form, it has been successfully deployed.It can be seen that there is a problem with my previous form. Because it is directly copied for use

1 Like
9

As you can see, this is a modified process file based on camunda, with some customized information added

10

Hello @wisdom ,

never mind. I am glad you solved the issue.

I did not mean the bpmn xml but the processes.xml file which is part of every Camunda Process Application. It describes how the process application should be deployed.

There, it could appear that you explicitely add a resource AND scan for resources on the classpath which would result in having the same resource in the deployment multiple times which would cause the same exception.

Jonathan