Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@ProcessApplication annotated classes are not scanned on server startup, processdefinitions not deployed #4898

Open
tvhdev opened this issue Jan 18, 2025 · 1 comment
Assignees
Labels
type:bug Issues that describe a user-facing bug in the project.

Comments

@tvhdev
Copy link

tvhdev commented Jan 18, 2025

Environment (Required on creation)

Camunda 7.22.0 on Dockerhub, run in Docker Desktop under an WSL environment

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)

Annotated class

@ProcessApplication("Wartungsankuendigung App")
public class WartungsankuendigungProcessApplication
extends ServletProcessApplication{}

is "not scanned" any more on server startup

Dependencies in pom.xml

 <properties>
    <camunda.version>7.22.0</camunda.version>
  </properties>
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.camunda.bpm</groupId>
        <artifactId>camunda-bom</artifactId>
        <version>${camunda.version}</version>
        <scope>import</scope>
        <type>pom</type>
      </dependency>
    </dependencies>
  </dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.camunda.bpm</groupId>
      <artifactId>camunda-engine</artifactId>
      <scope>provided</scope>
    </dependency>
    <dependency>
      <groupId>javax.servlet</groupId>
      <artifactId>javax.servlet-api</artifactId>
      <version>4.0.1</version>
      <scope>provided</scope>
    </dependency>
  </dependencies>

META-INF/processes.xml

<?xml version="1.0" encoding="UTF-8" ?>
<process-application
    xmlns="http://www.camunda.org/schema/1.0/ProcessApplication"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <process-archive name="wartungsankuendigung">
    <process-engine>default</process-engine>
    <resource>wartungsankuendigung.bpmn</resource>
    <resource>wartung-ergebnis.form</resource>
    <resource>wartung-zeitraum.form</resource>
    <properties>
      <property name="isDeleteUponUndeploy">true</property>
      <property name="isScanForProcessDefinitions">true</property>
    </properties>
  </process-archive>
</process-application>

Steps to reproduce (Required on creation)

update version of Camunda from 7.21.0 to 7.22.0 in Dockerfile

Observed Behavior (Required on creation)

Java Process Application is deployed, but "not started", Processes and forms are not deployed. the included "camunda-invoice" process application starts up normally. if the application is "recompiled" from the current github repo (tag 7.22.0), the invoice app does not deploy either!

Expected behavior (Required on creation)

Java Process Application should be deployed AND also start and deploy processes/forms in Camunda 7.22.0

Root Cause (Required on prioritization)

I dont know why it happens

Solution Ideas

Downgrade to 7.21.0

@tvhdev tvhdev added the type:bug Issues that describe a user-facing bug in the project. label Jan 18, 2025
@joaquinfelici joaquinfelici self-assigned this Jan 24, 2025
@joaquinfelici
Copy link
Contributor

joaquinfelici commented Jan 24, 2025

Hello @tvhdev , thanks for the report. This might be related to some upgrades in version 7.22, I suggest you check the 7.21 to 7.22 Migration Guide, for example the Tomcat 10 upgrade which mentions updating javax dependencies. If the issue persists, it could be useful to share the logs you get when the application isn't started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Issues that describe a user-facing bug in the project.
Projects
None yet
Development

No branches or pull requests

2 participants