Time Zone Issues with Java 1.4 on Windows
If your experiencing timezone problems with Java 1.4 on Windows, it may be due to this bug: #5033603, which was fixed in Java 1.5.
Basically when Java 1.4 looks up your timezone information to set the default timezone it looks in
HKEY_LOCAL_MACHINE/SYSTEM/ControlSet001/TimeZoneInformation first instead of just
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/TimeZoneInformation. It is possible that ControlSet001 is not your current control set, which is where the problems come in. You will see the correct timezone info in Windows Control panel but Java will be using the incorrect time zone.
This entry in the java discussion forums has lots of info describing the issue.
So to solve the problem you can update the registry settings manually, or your can set the system property at startup by adding
-Duser.timezone=America/New_York (or whatever your timezone is) to your VM Arguments.
- ColdFusion returning empty response with server-error: true
- Careful applying CF11u16, CF2016u8, CF2018u2
- Sessions don't work in Chrome but do in IE
- csrfVerifyToken does not invalidate the token
- The cf_sql_ is optional in cfqueryparam
- Cookie Expires / Max-Age 1969-12-31T23:59:59.000Z
- Burst Throttling on AWS API Gateway Explained
- How to Resolve Java HTTPS Exceptions