Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-3429

User wrongly gets success notification when a SchedulerException occurs in async action

XMLWordPrintable

    • Sprint 5 (Basel)
    • 1

      In AbstractCommandAction we don't deal with potential SchedulerExceptions, which are typically left uncaught, as they occur in another thread.

      This happens e.g. if the scheduler cannot instantiate the CommandJob (missing parameter candidate)

      As a result, the job is not executing at the time the action checks for it, and considers it done and successful.

        Acceptance criteria

              ilgun Ilgun Ilgun
              mgeljic Mikaël Geljić
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0d
                    0d
                    Logged:
                    Time Spent - 5h
                    5h