Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Job daemon produces multiple runs because of time change

    Job daemon produces multiple runs because of time change

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    Description:
    We find that even though we do not have jobs scheduled to run during the time change (day light saving), after the time change occurs in the fall, the job daemon produces two runs of *every* job (one hour apart), regardless of when the job was scheduled to run.

    It seems that stopping the job daemon during the time change and restarting it after prevents the problem, but then all the jobs which were supposed to run that night do not run. What we want and need is for the job daemon to be corrected so that it does not have this problem.

    Resolution:
    This will not be changed. You need to stop (util e/15/2) and re-start (util e/15/1) the daemon in this circumstance.

    Additional Information

    day light saving, time change, daemon


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • JBOSS port and protocol
      • Job daemon won't start; "No jobs in file"
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 16.02
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved