Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-44261

Use stateful quartz wrapper for SiteStats event aggregation job

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 20.1
    • Component/s: None
    • Labels:
      None
    • 21 Status:
      Resolved
    • Test Plan:
      Hide

      No regressions in SiteStats when configured to use event aggregation quartz job:

      collectThreadEnabled@org.sakaiproject.sitestats.api.StatsUpdateManager.target=false

      Show
      No regressions in SiteStats when configured to use event aggregation quartz job: collectThreadEnabled@org.sakaiproject.sitestats.api.StatsUpdateManager.target=false

      Description

      SiteStats should use the stateful wrapper for the quartz job to avoid jobs overlapping and having to check status.

      If the quartz job is executed while an existing job is still running, these lines show up in the logs:

      2020-09-10 14:38:00,023 WARN QuartzScheduler_Worker-2 org.sakaiproject.component.app.scheduler.jobs.SpringJobBeanWrapper - Non-stateful wrapper used with stateful job: org.sakaiproject.sitestats.api.StatsAggregateJob, use SpringStatefulJobBeanWrapper

      2020-09-10 14:38:00,023 WARN QuartzScheduler_Worker-2 org.sakaiproject.sitestats.impl.StatsAggregateJobImpl - Another instance of org.sakaiproject.sitestats.api.StatsAggregateJob is currently running - Execution aborted.

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

                Assignee:
                smarquard Stephen Marquard
                Reporter:
                smarquard Stephen Marquard
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Git Integration