[
https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin....
]
Serg Pol edited comment on WFLY-9610 at 1/10/18 8:56 AM:
---------------------------------------------------------
jobOperator.stop(executionId) has set BatchJobs in status STOPPING from status STARTING
and after a thread became available has stopped them and set them in status STOPPED.
To my sorrow these BatchJobs were really started (from status STARTING) before they were
stopped!
I thought that they will not be started/called at all in this case!
was (Author: serg_732173):
jobOperator.stop(executionId) has set BatchJobs in status STOPPING from status STARTING
and after a thread became available has stopped them and set them status STOPPED.
To my sorrow these BatchJobs were really started (from status STARTING) before they were
stopped!
I thought that they will not be started/called at all in this case!
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)