Leap Year Second Response

Version 4


    The International Earth Rotation and Reference Systems Service (IERS) has announced a leap second for 1st January 2017 (see reference). This means a positive leap second will be introduced at the end of December 2016. 


    The sequence of dates of the UTC second markers will be:

    2016 December 31, 23h 59m 59s

    2016 December 31, 23h 59m 60s

    2017 January   1, 0h 0m 0s


    The difference between UTC and the International Atomic Time TAI is:

    from 2016 July 1, 0h UTC, to 2017 January 1 0h UTC   : UTC-TAI = - 36s

    from 2017 January 1, 0h UTC, until further notice    : UTC-TAI = - 37s






    BSA Impact to BladeLogic Server Automation (BSA) customers

    BSA solutions currently use OS System Time and do not have any activities which are sensitive to sub-second latency.  Nevertheless, BSA 8.5 SP1 Patch 4 and prior versions require a restart of the app server.  BSA solutions after BSA 8.5 SP1 Patch 5 are already using java 1.7 update 71 or later versions and will not be affected. The rscd agent is not impacted by this for any of the BSA versions.


    Impact to BMC Cloud Lifecycle Management (CLM) customers

    During the insertion of leap second all active sessions to CLM will expire and in flight requests may potentially fail sometimes.

    However impact of this should be limited since there is going to be only one leap second inserted and only the active sessions/requests at that very moment may not go through.

    All subsequent request and sessions should ideally work without any restart required for platform manager or CLM UI components. However it is generally advised to restart the platform manager and other important components of CLM such as BSA App Server etc.

    Alternatively customers are advised to not start any critical operations just before the leap second insertion.


    BAO, BDA, BMA, BNA, and RLM are not affected by Leap Second 2016 issues.