Date/time parsing of DST times using Sun JRE 1.5 gives different behavior as compared to previous versions.

Date/time parsing of DST times using Sun JRE 1.5 gives different behavior as compared to previous versions.

book

Article ID: KB0086837

calendar_today

Updated On:

Products Versions
All Products -
Not Applicable -

Description

Description:
With JRE 1.5 and later, Sun introduced a change in behavior in the way that some DST times are handled.  When using non-lenient date parsing, a time of “2007-03-11 02:00:00” for example, will give an “Unparseable date” exception using JRE 1.5, whereas it would be converted to “2007-03-11 03:00:00” using previous versions of the JRE.  Sun considered this previous behavior to be a defect, which was corrected in 1.5.

The reason this is considered unparseable is because that time doesn’t exist in a local US timezone, and is considered invalid.  

With the recent shift in the US DST and the effect on many applications, it is possible that such data will be generated and the processing of such data will cause exceptions in TIBCO applications that rely on Java for date/time parsing.  An example would be the parse-dateTime() function of TIBCO BusinessWorks.

We are alerting you given the recent attention that is focused on DST issues, and the fact that the behavior is different depending on the JRE in use. If you notice exceptions related to this change in behavior, you will need to take appropriate recovery steps.

Issue/Introduction

Date/time parsing of DST times using Sun JRE 1.5 gives different behavior as compared to previous versions.