This is a SUNBUG for 100206: https://bugs.openjdk.java.net/show_bug.cgi?id=100206
Today I found that one computer jvm Calendar behaves differently than another
computer. Took me quite a while to figure out what is wrong.
The root cause was a comment in /etc/timezone which led the jvm to try and open
the comment as a file, fails and did not fallback to next method.
I know that there is a comment which explicitly assume no comments, no spaces
etc... but it is so simple to accept such standard format. Attached is a patch,
please consider to apply.
Another issue is that if I remove the /etc/timezone file, the jvm works as
expected, so maybe if the content of the /etc/timezone is an invalid, the jvm
should fallback to other methods.
TimeZone_md.c.diff attached to this report.