Clarity

Expand all | Collapse all

Cause of error "Illegal instant due to time zone offset transition" ?

Jump to Best Answer
  • 1.  Cause of error "Illegal instant due to time zone offset transition" ?

    Posted 10-16-2018 11:08 AM

    The new UX is having problems when users enter time in the timesheets.

    The visible error is:

     

    The error message in the app log is:

    Illegal instant due to time zone offset transition (America/Santiago)

     

    This only happened with time entries belonging to the last week (from "08-OCT-2018" to "14-OCT-2018").

    No problems detected in previous and further weeks.

     

    Any ideas?



  • 2.  Re: Cause of error "Illegal instant due to time zone offset transition" ?

    Posted 10-16-2018 01:03 PM

    Are your users in more than one timezone?

    Did change from daylight saving time to standard time occur during that timeperiod?



  • 3.  RE: Cause of error "Illegal instant due to time zone offset transition" ?

    Posted 10-08-2019 03:49 PM
    any ideas?


  • 4.  Re: Cause of error "Illegal instant due to time zone offset transition" ?

    Posted 10-16-2018 01:13 PM

    Hi. Users are in the same timezone.

    Currently, the change of daylight saving time occurs in August. Some years ago, the change occured in October (second saturday of October), but not anymore. We have patched the Java with TZUpdate after the rule was modified, so this old rule should not be valid anymore in Java.



  • 5.  Re: Cause of error "Illegal instant due to time zone offset transition" ?

    Posted 10-16-2018 01:19 PM

    You might want to google for the error

    org.joda.time.IllegalInstantException: Illegal instant due to time zone offset transition (daylight savings time 'gap') … 

    On the otherhand can you verify that the patch is actually still in use.



  • 6.  RE: Cause of error "Illegal instant due to time zone offset transition" ?
    Best Answer

    Broadcom Employee
    Posted 10-13-2019 04:51 AM
    Can you share the properties.xml and i have seen similar error due to a parameter missing in the JDBC URL and here is the article i wrote https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=136098

    ------------------------------
    Thanks & Regards
    Suman Pramanik
    Principal Support Engineer | Customer Success & Support, Enterprise Software Division
    Broadcom
    ------------------------------