-
Enhancement
-
Resolution: Done
-
Major
-
24.0.0.Final
-
None
Currently BatchJobExecutionResource.refreshChildren() method first loads all job instances by job name, and iterate through job instances to get job executions for each job instance. This is not efficient and has resulted in too many db queries, and sometimes high memory consumption and frequent GC activities.
A more efficient way is to be able to retrieve all job executions belonging to a job in one operation.
- blocks
-
WFLY-14966 Switch to Jakarta artifacts in batch subsystem and tests
- Resolved
- is cloned by
-
JBEAP-22172 (7.4.z) More efficient way of getting batch job executions by job name
- Closed
- is related to
-
JBERET-506 Support retrieving job executions by job name
- Resolved
- relates to
-
WFLY-7418 Batch deployments with a large number of executed jobs can lock up or slow down the web console
- Pull Request Sent
-
WFLY-14275 Large job repository is blocking deployment
- Closed
-
WFLY-14952 Upgrade jberet-core from 1.3.8.Final to 1.3.9.Final
- Closed