Camunda 7 failed to start after migration to Spring Boot 3

[spray]

In out project we are just updating dependencies to Spring Boot 3, Java 21 and Camunda 7.20.0 (from 7.18.0).
After bumping Camunda dependency to latest version we got the following exception during application start

Caused by: org.camunda.bpm.engine.ProcessEngineException: ENGINE-08043 Exception while performing 'Deployment of Process Application camundaConfiguration' => 'Deployment of process archive 'null': ENGINE-08006 IOException while scanning archive '/root/nested:/root/app-0.0.1-SNAPSHOT.jar'.

Caused by: org.camunda.bpm.engine.ProcessEngineException: ENGINE-08006 IOException while scanning archive '/root/nested:/root/app-0.0.1-SNAPSHOT.jar'.

Caused by: java.nio.file.NoSuchFileException: nested:/root/app-0.0.1-SNAPSHOT.jar

I have no idea why but Cammunda found during startup two processes.xml instead of one.

2023-12-22T13:35:11.467Z  INFO 1 --- [           main] org.camunda.bpm.container                : ENGINE-08024 Found processes.xml file at jar:file:/root/rea-contracts-0.0.1-SNAPSHOT.jar!/META-INF/processes.xml

2023-12-22T13:35:11.601Z  INFO 1 --- [           main] org.camunda.bpm.container                : ENGINE-08024 Found processes.xml file at jar:nested:/root/app-0.0.1-SNAPSHOT.jar/!BOOT-INF/classes/!/META-INF/processes.xml

In this project we have following configuration:
Dependencies

camunda-bpm-spring-boot-starter
camunda-bpm-spring-boot-starter-rest
camunda-bpm-spring-boot-starter-webapp

Configuration

camunda:
  bpm:
    authorization.enabled: true
    filter:
      create: All tasks
    deployment-resource-pattern: classpath:META-INF/processes/*.bpmn
    generic-properties:
      properties:
        enforce-history-time-to-live: false
        generalResourceWhitelistPattern: "[a-zA-Z0-9_]+|camunda-admin"

processes.xml

<process-application
        xmlns="http://www.camunda.org/schema/1.0/ProcessApplication"
>

    <process-archive>
        <properties>
            <property name="isDeleteUponUndeploy">false</property>
            <property name="isScanForProcessDefinitions">true</property>
        </properties>
    </process-archive>

</process-application>

And also we run Camunda using @EnableProcessApplication

Could you please advice how we should configure our app to be able to solve this issue? I tried manually configuring Camunda using @ProcessApplication and SpringBootProcessApplication but in this configuration I’m not able to set <property name="isDeleteUponUndeploy">false</property> and <property name="isScanForProcessDefinitions">true</property> which is needed in this project.

Thanks in advance

[Yana]

Hi @spray,

Welcome to the forum.

Did you manage to resolve the issue already?
If not, could you please share a minimal example project that replicates the issue so we can investigate further. Otherwise, please attach the pom.xml file.

Best,
Yana

[spray]

Hey,
thanks for replay.

Yup, I’ve managed this issue by downgrading project dependencies to Camunda 7.20.0 and Spring Boot 3.1.7.