[
https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin....
]
Cheng Fang commented on WFLY-9610:
----------------------------------
So the batch status transition is:
STARTING -> STOPPING -> STOPPED
If the stop request is issued early enough (while the job execution is still waiting for
available threads), the job execution batch status will be set to STOPPING, and from
STOPPING the only outcome is STOPPED. So how do you know "these BatchJobs were
really started (from status STARTING) before they were stopped!"? What part of the
application code is executed that you don't expect them to be executed?
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)