Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-30987

QuartzScheduler unable to start creating build failure during JSF ftest

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2021.20
    • Component/s: Scheduler

      Description

      The error in the ftest logs create a build failure (the same kind of errors we observe in nuxeo):

      01:46:31  [Text Finder] Searching for pattern '.*ERROR.*' in file set 'ftests/**/log/server.log'...
      01:46:32  /home/jenkins/workspace/nuxeo_lts_nuxeo-jsf-ui_2021/ftests/nuxeo-jsf-ui-hotreload-tests/target/tomcat/log/server.log:
      01:46:32  2022-04-26T23:28:27,162 ERROR [Thread-25] [org.quartz.core.QuartzScheduler] Unable to start scheduler after startup delay.
      01:46:32  [Text Finder] Finished searching for pattern '.*ERROR.*' in file set 'ftests/**/log/server.log'.
      01:46:32  [Text Finder] Setting build result to 'FAILURE'.
      

      The full log:

      2022-04-26T23:28:23,017 INFO  [http-nio-0.0.0.0-8080-exec-2] [org.nuxeo.runtime.reload.ReloadComponent] After updating Nuxeo server
      ======================================================================
      = Component Loading Status: Pending: 0 / Missing: 0 / Unstarted: 0 / Total: 752
      ======================================================================
      2022-04-26T23:28:23,017 INFO  [http-nio-0.0.0.0-8080-exec-2] [org.nuxeo.runtime.reload.ReloadComponent] Hot reload was done in 5607 ms, detailed steps:
      - flush: 2 ms
      - stop/standby: 2229 ms
      - undeploy-bundles: 7 ms
      - delete-copy: 0 ms
      - reload-resources: 0 ms
      - start/resume: 2636 ms
      - deployment-preprocessor: 727 ms
      - reload-properties: 0 ms
      2022-04-26T23:28:27,162 ERROR [Thread-25] [org.quartz.core.QuartzScheduler] Unable to start scheduler after startup delay.
      org.quartz.SchedulerException: The Scheduler cannot be restarted after shutdown() has been called.
      	at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:529) ~[?:?]
      	at org.quartz.core.QuartzScheduler$1.run(QuartzScheduler.java:564) [quartz-2.3.2.jar:?]
      	at java.lang.Thread.run(Thread.java:829) [?:?]
      

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: