Environment:

• OS: Linux (Manjaro / Ubuntu)
• WildFly 22
• Camunda 7.15
• Maven 3.8.2
• OpenJDK 11.0.12

Camunda/WildFly was downloaded here:

https://downloads.camunda.cloud/release/camunda-bpm/wildfly/7.15/

Description:

Given is a Singleton with automatic startup (@Startup annotation).

When an exception is thrown in the @PostConstruct handler, the WildFly rolls back the deployment. The @PreDestroy handler is called and the WildFly removes the content.

When adding a Camunda @ProcessApplication, the WildFly stucks in the deployment until a timeout happens. The WildFly is then broken and e.g. cannot be stopped anymore. The process has to be killed and the WildFly must be restarted.

Steps to reproduce / Observed Behavior:

Error case:

• Start WildFly 22 with Camunda integration
• Build and deploy the application (WAR) which is provided here:
  https://github.com/timonzi/camunda-predestroy
• ==> The WildFly does not stop the deployment
• ==> A normal shutdown is not possible anymore / The WildFly is unstable

Working case:

• Start WildFly 22 with Camunda integration
• Remove the process application  (CamundaProcessApplication.java) from the mentioned project
• Build and deploy the application (WAR)
• ==> The WildFly stops the deployment / The @PreDestroy annotated method is called

When using WildFly 20 and Camunda 7.14.0 it works fine!

Expected behavior:

The deployment should fail and be rolled-back when an exception is thrown.

Hints:

I also tested with WildFly 23 and Camunda 7.16 (Alpha). Here the same problem as in WF 22 and Camunda 7.15 happens.

You can find the logs for the working case (without @ProcessApplication) and the problematic one in the attachment of this issue.

I created also a post in the forum: 

https://forum.camunda.org/t/wildfly-deployment-cannot-be-rolled-back/30326