springboot+flowable 开发工作流 本地环境启动正常，在Linux下如下异常

[qq_34334124]

Exception while autodeploying process definitions. This exception can be ignored if the root cause indicates a unique constraint violation, which is typically caused by two (or more) servers booting up at the exact same time and deploying the same definitions.
org.flowable.common.engine.api.FlowableException: The deployment contains process definitions with the same key (process id attribute), this is not allowed
at org.flowable.engine.impl.bpmn.deployer.BpmnDeploymentHelper.verifyProcessDefinitionsDoNotShareKeys(BpmnDeploymentHelper.java:56)
at org.flowable.engine.impl.bpmn.deployer.BpmnDeployer.deploy(BpmnDeployer.java:79)
at org.flowable.engine.impl.persistence.deploy.DeploymentManager.deploy(DeploymentManager.java:62)
at org.flowable.engine.impl.cmd.DeployCmd.executeDeploy(DeployCmd.java:123)
at org.flowable.engine.impl.cmd.DeployCmd.execute(DeployCmd.java:68)
at org.flowable.engine.impl.cmd.DeployCmd.execute(DeployCmd.java:43)
at org.flowable.engine.impl.interceptor.CommandInvoker$1.run(CommandInvoker.java:51)
at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperation(CommandInvoker.java:93)
at org.flowable.engine.impl.interceptor.CommandInvoker.executeOperations(CommandInvoker.java:72)
at org.flowable.engine.impl.interceptor.CommandInvoker.execute(CommandInvoker.java:56)
at org.flowable.engine.impl.interceptor.BpmnOverrideContextInterceptor.execute(BpmnOverrideContextInterceptor.java:25)
at org.flowable.common.engine.impl.interceptor.TransactionContextInterceptor.execute(TransactionContextInterceptor.java:53)
at org.flowable.common.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:71)
at org.flowable.common.spring.SpringTransactionInterceptor$1.doInTransaction(SpringTransactionInterceptor.java:49)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:133)
at org.flowable.common.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:46)
at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)
at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56)
at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:51)
at org.flowable.engine.impl.RepositoryServiceImpl.deploy(RepositoryServiceImpl.java:97)
at org.flowable.engine.impl.repository.DeploymentBuilderImpl.deploy(DeploymentBuilderImpl.java:209)
at org.flowable.spring.configurator.DefaultAutoDeploymentStrategy.deployResources(DefaultAutoDeploymentStrategy.java:62)
at org.flowable.spring.SpringProcessEngineConfiguration.autoDeployResources(SpringProcessEngineConfiguration.java:116)
at org.flowable.spring.SpringProcessEngineConfiguration.lambda$start$0(SpringProcessEngineConfiguration.java:204)
at org.flowable.spring.SpringProcessEngineConfiguration$$Lambda$27/1218622610.accept(Unknown Source)
at java.util.ArrayList.forEach(ArrayList.java:1234)
at org.flowable.spring.SpringProcessEngineConfiguration.start(SpringProcessEngineConfiguration.java:204)
at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:175)
at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:50)
at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:348)
at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:151)
at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:114)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:880)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.finishRefresh(EmbeddedWebApplicationContext.java:144)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1118)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1107)
at com.mapabc.fos.Application.main(Application.java:21)
14:54:07.437 logback [main] INFO
===============================================
process文件夹下的流程定义文件并没有重复的process ID 表清空重启还是同样问题，不知论坛上有没有熟悉flowable的大神，

[qq_34334124]

自己顶一下吧

[qq_34334124]

要沉帖子啦！有大神吗？

[qps2009]

The deployment contains process definitions with the same key (process id attribute), this is not allowed 渣翻：流程部署包含有相同key(流程id属性)的流程定义，这不被允许。 是不是你的linux上存在多个流程xml文件，并且这些xml文件里面的process id是一样的？

[qq_34334124]

回复2楼：在整个服务器上就这样这个服务有流程文件，且只有两个流程文件，processID是完全不一样的两个名字，奇怪的是在Windows和unix下都可以正常使用，在Linux下就出这个问题。不知道还有没有其他的原因，已经试过啦2台不同的linux服务器啦

[qq_34334124]

@qps2009 s是一样的，直接部署上去的

[qps2009]

Windows和unix下的流程文件和linux下的流程文件是一样的吗？

[爱钓鱼的小钻风]

你解决了吗。我也遇到了，在windows非常正常
在linux就出现不同的错误