[
https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin....
]
Cheng Fang commented on WFLY-9610:
----------------------------------
After a job execution is submitted, a new job execution entry is created and inserted into
job repository db, whether it will be on hold or not. And the next time it is updated to
the db is when the job execution gets the chance to run with available thread and so it
can update itself into the db with new batch status.
the change to {{org.jberet.runtime.runner.JobExecutionRunner}}:
https://github.com/jberet/jsr352/commit/f27fb499aea1232bec1ee8050cb995e37...
The real change is moving the end curl brace from line 50 to line 84 to expand the if
condition block so that the processing is skipped in case of STOPPING.
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)