Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3868

Domain mode shutdown of EE executor service with :stop() or :stop(timeout=0) command doesn't work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.0.0.Alpha1
    • 5.0.0.Beta4
    • Management
    • None
    • Hide

      The test case simply schedules an instance of task ReSchedulingTask once
      the web app is activated (via the ServletContextListener hook)
      Each instance of ReSchedulingTask sleeps for 10 seconds and then
      re-schedules another instance of its own class.

      Invoking the following stop command doesn't seem to work
      /host=master/server-config=server-one:stop()
      /host=master/server-config=server-one:stop(timeout=0)

      This works /host=master/server-config=server-one:stop(timeout=1)

      • Simply drop the test app into the default domain config

      Reproducible in EAP 7.1.2, 7.1.1, 7.1.0, & 7.0.9

      Show
      The test case simply schedules an instance of task ReSchedulingTask once the web app is activated (via the ServletContextListener hook) Each instance of ReSchedulingTask sleeps for 10 seconds and then re-schedules another instance of its own class. Invoking the following stop command doesn't seem to work /host=master/server-config=server-one:stop() /host=master/server-config=server-one:stop(timeout=0) This works /host=master/server-config=server-one:stop(timeout=1) Simply drop the test app into the default domain config Reproducible in EAP 7.1.2, 7.1.1, 7.1.0, & 7.0.9

    Description

      EAP's EE-Concurrency Managed Executor Service is expected to skip the tasks that are pending in its execution queue upon server shutdown as documented here
      This is necessary to cope with scenario where a polling-type task is re-scheduling a new instance of itself just before exiting (so that there is always one task polling - pattern used e.g. by Spring message listeners

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-14753 [GSS](7.1.z) Domain mode shutdown of EE executor service with :stop() or :stop(timeout=0) command doesn't work

          • 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. JBEAP-15058 (7.1.z) Automated test for JBEAP-14753

          • 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

              yborgess1@redhat.com Yeray Borges Santana
              yborgess1@redhat.com Yeray Borges Santana
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: