Always execute ThreadPoolTaskExecutor callbacks on thread pool threads

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.11
    • Affects Version/s: None
    • Component/s: Networking
    • None
    • Fully Compatible
    • ALL
    • Service Arch 2019-04-22, Service Arch 2019-05-06
    • 5
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Rather than relying on failure to schedule work onto the background thread pool as the mechanism for failing scheduled (but not run callbacks), wait to join the executor until after all jobs have cleared through.

      I.e. join the thread pool in task executor join(), after all pool processing jobs are gone, instead of in shutdown()

              Assignee:
              Mira Carey
              Reporter:
              Mira Carey
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: