18.0.1.Final, 19.0.0.Beta3, 20.0.0.Beta1
Download wildfly 18.0.1.Final & extract & use wildfly-18.0.1.Final Checkout hielkehoeve/wildfly/18.0.x Build test project (testsuite/integration/batch-jberet/ WFLY-13162 ) Copy standalone/configuration/standalone-full.xml to standalone/configuration/standalone.xml Start wildfly in standalone mode Redeploy project.ear a number of times (testsuite/integration/batch-jberet/ WFLY-13162 /project-ear/target/project.ear)
- Download wildfly 18.0.1.Final & extract & use wildfly-18.0.1.Final
- Checkout hielkehoeve/wildfly/18.0.x
- Build test project (testsuite/integration/batch-jberet/
- Copy standalone/configuration/standalone-full.xml to standalone/configuration/standalone.xml
- Start wildfly in standalone mode
- Redeploy project.ear a number of times (testsuite/integration/batch-jberet/
Because of a thread unsafe construction in WildFlyJobXmlResolver I am experiencing ConcurrentModificationExceptions while starting my EAR every so often. This is because every EJB of the EAR is processed by WildFlyJobXmlResolver in paralel threads. Even if it has no jbatch dependency or dependency to a EJB which does.
This is not reproducable for every startup as it depends on the performance of the host machine, number of ejbs in ear, number of threads and thread timing.
I have created an example project representing our project setup with which I am able to reproduce the issue using a default wildfly build. This test project contains 1 EJB with jbatch, a number of plain EJBs, a WAR which uses the jbatch EJB and an EAR.
See below for the exception stacktrace.
I have made a small fix for this issue @ https://github.com/hielkehoeve/wildfly/commit/82047233621c3e5bdbd45333ca4c5c04bfd0d2cb. The example test project can also be found there.