Understanding the Strange Behavior of SimpleDateFormat in Java

Explore why `SimpleDateFormat` can produce unexpected parsing results and learn how to handle date-time format correctly in Java.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Strange behavior of SimpleDateFormat

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Strange Behavior of SimpleDateFormat in Java

When working with date and time in Java, developers often turn to the SimpleDateFormat class for its convenience. However, some users have encountered strange behavior when parsing strings that appear to be in the correct date format. In this post, we’ll explore a specific example that unveils issues with SimpleDateFormat and suggest better alternatives for date handling in Java.

The Problem

Consider a situation where you are attempting to parse a string representation of a date using SimpleDateFormat with the desired pattern. The expected outcome is simple: if the input string does not match the format, a ParseException should be thrown. However, unexpected inputs yield surprising results. For instance:

[[See Video to Reveal this Text or Code Snippet]]

This input works perfectly. But upon entering erroneous inputs like:

123-20221114-12:34:56.789 — Result: Sun Feb 15 12:34:56 CET 728

12320221114-12:34:56.789 — Result: Mon Nov 21 12:34:56 CET 1289

You might expect to see a ParseException thrown, but this is not the case. What is going on here?

Analyzing the Output

The strange outputs can be attributed to how SimpleDateFormat interprets the input strings. Here’s a breakdown of what happens behind the scenes for these erroneous examples:

Input: 123-20221114-12:34:56.789

Parsed As: year 123, month -2, day 221114

Input: 12320221114-12:34:56.789

Parsed As: year 1232, month 02, day 21114

As seen, the SimpleDateFormat does not strictly enforce the importance of the input being accurate. Instead, it continues to read values based on currently available segments adhering to the provided format. This leads to unexpected results which, at first glance, seem puzzling.

The Solution: Switching to Better Alternatives

Using the DateTimeFormatter

Instead of relying on SimpleDateFormat, the DateTimeFormatter class is recommended:

[[See Video to Reveal this Text or Code Snippet]]

Improved Parsing: The new API strictly controls the parsing process, immediately throwing exceptions for unrecognizable input.

Immutable and Thread-safe: This enhances the reliability of your code in multi-threaded environments.

Conclusion

If you're still using SimpleDateFormat, consider upgrading your code to use DateTimeFormatter for better performance and reliability in handling dates in Java.