There is a default TZ in the JDK which is TRYING to be the same TZ as the OS, but when it wakes up and if it can't map from something it sees to something it knows or alternatively can now map from something it didn't know before to something it now does, then the behavior could change across JDK releases.
This is probably NOT the case that we used to have way back in the dark ages of Java. Originally the default TZ become "Pacific Time" (aka "America/Los Angeles" etc.), if the original attempt at setting couldn't find a good match (well the code WAS written in California), but ever since about 1.3 the fallback value has been UTC. Combining the above two paragraphs, one or the other of your JVMs might be running not on local time, but on UTC. HTH, -Paul Dan Rollo wrote: > Good point. Both jdk's are on the same Ubuntu machine. I assume the TZ's > are the same, as I never took any action to change them. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Joda-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/joda-interest
