Yesterday I blogged briefly about what I thought was a problem with our JVM version for JRun and the daylight savings change.
While our server had the right time CF was displaying the time with a two hour differential. So I downloaded the hot fix from Sun and installed it and restarted the server. We have the debugging in a separate window and it shows both the date and time and low and behold the time was correct! And I was happy.
So I continued working in the application and all of a sudden I noticed that the time was once again two hours off! How in the hell could that happen in the middle of using the application?
As it turns out, and after about a full day tracing through and finally pinpointing the offending code, the problem results from a third party Java component that we are using.
The Java component converts Gregorian dates to Hijiri and visa versa. I took a look at the class file and noticed that even though the dates are passed back and forth as strings the programmer for some reason sets the timezone to GMT in the init method which of course set CF's server timezone. This "little" problem then presents itself to all applications that happen to be running on that server!
Now we just have to wait for the update from the vendor.
No recent entries.