Re: NSTimestamp problem
Re: NSTimestamp problem
- Subject: Re: NSTimestamp problem
- From: Colin Curtin <email@hidden>
- Date: Wed, 10 Jan 2007 12:48:51 -0800
This solution appears to cause problems with our apps. We get this
in the WO app log when starting up:
ZoneInfo: wrong magic number: UTC
ZoneInfo:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/zi/ZoneInfoMappings
(No such file or directory)
Any ideas?
It appears to me that the zoneinfo files in /usr/share/zoneinfo
and those in the JavaVM framework have different magic numbers as the
first error message indicates:
Yes, after looking through our logs, this is the case. After removing
the 'zi' directory entirely, the VM reverted to using UTC. It seems our
magic trick didn't do much of anything ;)
After finding this, I tried copying the java Phoenix zoneinfo file and
replacing the java Los_Angeles one with it:
# cd
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/zi/America
# sudo mv Los_Angeles Los_Angeles.old
# sudo cp Phoenix Los_Angeles
Phoenix doesn't switch to DST, so this seemed to fix it. I'm hesitant to
use it - timestamps set now for mid-April might be an hour behind.
I hate time.
But since our data entry app only uses timestamps for checking date and
not datetime, we should be okay.
I'll take a look at javazic and see how it does at compiling zoneinfo
text files.
Whoopee,
Colin
--
Colin Curtin
Programmer, Kavli Institute for Theoretical Physics
UCSB
web: http://www.kitp.ucsb.edu
email: email@hidden
office: 805.893.6396
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden