RE: System Date.

[OMurchu, Oisin]

Title: Message

make sure its not a serialisation problem - the Calendar is transient in a Date object, and it effectively holds the TimeZone, so if you have a different timezone on 2 boxes and serialise a date object between them, the milliseconds since 1970 is serialised, but the relevant time zone that it was calculated with is not. So when the Date is recreated, it is done with the local default time zone, but using a time in milliseconds from a different timezone, and discrepencies ensue.

 

hope this helps,

 

Oisín.

-----Original Message-----
From: Geoff Soutter [mailto:[EMAIL PROTECTED]]
Sent: 13 February 2002 00:05
To: Orion-Interest
Subject: RE: System Date.

I've had problems with Java timezones before. As I remember, Unix inherits timezone settings from it's environment. Did you run your java test class with the same environment as Orion (eg the same user)?

 

geoff

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Troy Gibson
Sent: Wednesday, 13 February 2002 6:00 AM
To: Orion-Interest
Subject: System Date.

Having trouble with system Date. In Orion our application converts dates based on our users time zone. For some reason our application is producing incorrect date times. The same piece of code when ran on its own as a Java class produces correct time conversions. Are there environment variables that Orion uses that may cause it to interprets the system date differently than what the system date really is? We use a staging and production instances of Orion running on two different Unix boxes. Both boxes have the same system date, the application running on staging produces correct dates, the one on production does not, further evidence that maybe the problem lies with the Orion instance and not the code or the servers.

Thanks for any ideas you may have.