Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11139

Exception from getRunningExecutions method causes undeployment to hang

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 14.0.0.Final
    • Batch
    • None

    Description

      When undeploying a batch application, or stopping the server with active batch application deployment, the batch subsystem tries to get all running batch job executionsm, and to stop them before undeploying the application or shutting down the server.

      When exceptions occurs from calling batchJobReposiotory.getRunningExecutions, the undeployment operation hangs. This happens to both in-memory and jdbc batch job repository. These exceptions may be caused by database server down, or connection timeout, for instance.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17944 [GSS] (7.2.z) undeploy and shutdown hang by JdbcRepository error

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15589 [GSS] (7.1.z) undeploy and shutdown hang by JdbcRepository error

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBERET-458 getRunningExecutions() should look in cache as fallback

          • 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

          Activity

            People

              weli@redhat.com Weinan Li
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: