Job executor may leave jobs locked when unregistering engine or shutting job executor down

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: engine
    • None

      With the improvements made in CAM-4400, in case jobs cannot be submitted to the execution queue they are no longer executed by the acquiring thread but deferred for re-submission in the next acquisition cycle. This essentially means there is a context of acquired-not-yet-executed jobs shared between subsequent job acquisition cycles. However, between two cycles an engine may be unregistered or the job executor may be shut down. In such cases, the currently pending jobs are not unlocked, so when immediately restarting the job executor (or re-registering the engine), some jobs are only re-attempted when the lock expires.

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: