-
Bug
-
Resolution: Done
-
Critical
-
7.4.0.GA
-
None
We are updating from WildFly 13 (jberet 1.2.4) to WildFly 21.0.2 (jberet 1.3.7).
In our production environment we are running about 50 jobs, some of them in a frequency of 2 or 4 minutes. For documentation reasons we only can delete job information older than 3 months. So we have 20000 and more jobinstances per job in our job repository - an oracle database job repo.
Deploying of our Job-Module to WildFly 21 is never finished - sometimes a out of memory exception is thrown.
Note: this issue only provides partial solution - it avoids excessive refreshing of job executoins as described in this comment. Another fix is to be brought by the follow up issue JBEAP-22172.
- clones
-
WFLY-14275 Large job repository is blocking deployment
- Closed
- is cloned by
-
JBEAP-21992 [GSS](7.3.z) WFLY-14275 - Large job repository is blocking deployment
- Closed
- is related to
-
JBEAP-22172 (7.4.z) More efficient way of getting batch job executions by job name
- Closed