I’m trying to upgrade from Camunda 7.18.0-ee/WildFly26/javax to Camunda 7.23.0-ee/WildFly35/jakarta and I’m running into a class loading issue that seems to be new to the upgraded environment.
I have a .war that contains:
- a
.bpmnprocess - a
JavaDelegatethat is invoked by aServiceTaskin the process - a
RESTendpoint that triggers the start of the process thru our native Camunda abstraction layer
When the endpoint is hit the process successfully executes in our old env.
In the upgraded env I get the following class loading error:
Caused by: org.camunda.bpm.engine.ClassLoadingException: ENGINE-09017 Cannot load class 'com.bpm.foo.bar.MyJavaDelegate': com.bpm.foo.bar.MyJavaDelegate from [Module "org.camunda.bpm.camunda-engine" version 7.23.0-ee from local module loader @70f59913 (finder: local module finder @77258e59 (roots: C:\MyCamundaWF35Server\modules,C:\MyCamundaWF35Server\modules\system\layers\base))]
For some reason the process engine is looking in the WildFly modules for the JavaDelegate instead of the .war deployment.
If I fudge the name of the process in our old env (so as to produce the same exception) you can see that it’s correctly looking for the Class in the .war deployment:
Caused by: org.camunda.bpm.engine.ClassLoadingException: ENGINE-09017 Cannot load class 'com.bpm.foo.bar.MyJavaDelegateBad': com.bpm.foo.bar.MyJavaDelegateBad from [Module "deployment.my-rest-test-process.war" from Service Module Loader]
Any ideas on what might be causing this?
Thanks much.