[
https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin....
]
Serg Pol commented on WFLY-9610:
--------------------------------
this delayed BatchJob is executed later if free thread appears, according my test.
Is it possible to manage execution of delayed BatchJobs with status STARTING? To switch it
off?
For example if BatchJob wasn't started because of no available free threads than it
will not be started any more later, for example in half hour.
Starting of BatchJobs in wrong time because of no available free threads now can be bad
for some tasks-use cases.
Start of a BatchJob is called, but BatchJob is seems no started.
Absent entries in DB tables step_execution, job_execution
--------------------------------------------------------------------------------------------------------------------------
Key: WFLY-9610
URL:
https://issues.jboss.org/browse/WFLY-9610
Project: WildFly
Issue Type: Bug
Components: Batch
Affects Versions: 9.0.1.Final
Environment: Cluster, standalone-full-ha
Reporter: Serg Pol
Assignee: Cheng Fang
Start of a BatchJob is called and record/entry is absent sometimes in DB table
"step_execution" as well as Endtime and Exitstatus in the table job_execution
(there is just info about start of BatchJob).
There are no any error nessages.
BatchJob is not started in this case according Log.
Any idea? Thanks
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)