Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-21442

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

    XMLWordPrintable

Details

    Description

      The following problem was reported by user:

      I have 2 JBoss instances sharing the same JobRepository. So on both instances one can see the executions for both instances. When I start an Execution on - let's say - node 1 and restart that same execution on node 2, then node 2 will start a new Execution starting from the last commited checkpoint while the first Execution keeps running on node 1. So now I have two Executions processing the same Items.

      When I check the status of the Execution running on node 1 from node 2, I can see that it is in STARTED state. But the JobOperators ignores that and restarts it anyway.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBERET-509 Restart batch job execution from a different node

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21126 [GSS](7.3.z) JBERET-509 - Restart batch job execution from a different node

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-21777 [GSS](7.4.z) Upgrade jberet from 1.3.7.Final-redhat-00001 to 1.3.9.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-21804 [GSS](7.4.z) WFLY-14619 - Stop batch job execution from a different node

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              istudens@redhat.com Ivo Studensky
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: