Another quick one tonight.
At work, I use BusinessObjects Enterprise which runs on top of a Java platform. After daylight savings had clicked over a colleague brought to my attention that object timestamps were now one hours behind what they should be. This turned out to be an issue with the timezone data in the version of Java bundled with BusinessObjects Enterprise (as it is much older than the current release).
The solution was to run the Timezone Updater Tool (TZUT) on the affected machine which would update all Java installations with the correct timezone information. Theoretically, we could have just shutdown the application and then the Java platform followed by restarting them both but to be safe we restarted the virtual machine. All was well after the relatively painless exercise.
So, if you use Java-based applications at work (either server of client software) then you might need to run the TZUT just to be safe. Don’t assume that if it has just been installed then it should be fully patched out of the box. Of course, if you keep up to date with the latest Java releases then you should have no problems.
Follow Us!