Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Done
Priority: Major
Fix Version/s: 7.4.1.CR1, 7.4.1.GA
Affects Version/s: None
Component/s: Batch
Labels:
- downstream_dependency
- test_included

Blocked:
False
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
+
Release Note Text:
Undefined
Target Release:

7.4.z.GA
Git Pull Request:
https://github.com/jbossas/jboss-eap7/pull/4001
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

When stopping a batch job execution, jberet currently keeps the batch status STOPPING in memory only, and only persist the batch status after the job execution has been stopped.

Strictly speaking, the batch status STOPPING should be persisted to job repository immediatly to truly reflect its execution status. To support that, JobRepository interface and its impl in WildFly JobRepositoryService will need to be updated with additional operation.

clones

WFLY-14619 Stop batch job execution from a different node

Closed

is blocked by

JBEAP-21777 [GSS](7.4.z) Upgrade jberet from 1.3.7.Final-redhat-00001 to 1.3.9.Final-redhat-00001

Closed

is cloned by

JBEAP-21805 (7.3.z) WFLY-14619 - Stop batch job execution from a different node

Closed

relates to

JBEAP-21442 [GSS](7.4.z) JBERET-508 - Restart batch job execution from a different node

Closed

Assignee:: Bartosz Spyrko-Smietanko

Reporter:: Bartosz Spyrko-Smietanko

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2021/05/04 9:59 AM

Updated:: 2024/08/27 1:54 PM

Resolved:: 2021/07/29 7:52 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates