Daylight Savings Time
Fri, 2007-02-02 16:40 — Geissler
I'm on Luminis Platform 3.3.1.9 build 9 (on a Windows 2000 SP4) box.
I was wondering if any of you are concerned about the Daylight Savings Time change since the java version for that release is 1.3.1_13-b03 and it appears that the new DST is not handled until 1.3.1_19.
There's an article about it at Customer Support Center (1-1LW92R Java Daylight Saving Time Changes in 2007 - Luminis Platform).
I've gotten confirmation that Luminis shouldn't have problems continuing to run, but I just wanted to do a sanity-check.
Thanks!
Hack Your Knowledge
Recent blog posts
- Luminis IV GCF Single Sign On with OSX=Failure PC=Working
- Cisco 4710 - Load Balancer
- First CPIP - ERROR
- Luminis Developer Job Available w/ Stable Organization
- Luminus Developer Job
- SSO to SSB mixed content error in IE
- Avoid email sending when add or delete user from group
- Luminis components
- Luminis 4 & Groupwise 7
- Luminis Developer Needed for Position w/ Stable Organization
Developer Links
Poll
What version of Lumins / OS are you running in production?
Luminis 4.x - Linux
21%
Luminis 4.x - Windows
8%
Luminis 4.x - Solaris
31%
Luminis 3.x - Windows
17%
Luminis 3.x - Solaris
19%
Luminis 3.x - Linux (if so - we need to talk) <G>
4%
We gave up on Luminis - I just like this site !
0%
Total votes: 52
- Login or register to post comments
- Older polls
Syndicate
Please elaborate
We're running 3.3.1.57 (Solaris platform) and do plan to upgrade to 3.3.3.64 but had not planned on doing so before the DST change.
Please elaborate on what part(s) of Luminis may be affected by the DST change.
Has anyone applied the JDK change to a pre-3.3.3 release?
Has anyone replaced the Calendar timezones.ics file with the one available on the support site?
Thanks,
Genetha Smith, WSU
My exchange with the CSC...
This is the transcript. I don't have an answer to my last question yet (I asked on 2/2).
[Me] Will luminis have serious problems if I do not apply the upgrade/hotfix? Is this an emergency?
[CSC support] No, Luminis will continue to work fine without this update. The events will just 'skip ahead' in April instead of March. As far as it being an emergency, that will have to be your call.
Please let me know if you have any questions.
[Me] Thanks, would you please clarify what you mean by "events"? We're not using LDI to trigger events from Banner. Is that what you mean? As far as the calendar, it seems I just need to use the .ics file. Is that correct?
any more input
We are running 3.3.16 (or will be) on solaris, anyone know if this will cause an issue?
What we did
We are running HP-UX OS with LP3.3.1.64 currently.
Our systems are broke out like this:
web/user ldap on hpux
email on hpux
calendar on hpux
oracle db on hpux
lmg 3.1/lmb on windows using cygwin
On HPUX:
All HPUX boxes require some HP OS patches. All luminis/products/jdk need to be 1.3.1_18 or higher http://java.sun.com/developer/technicalArticles/Intl/USDST/
Email server has some jars/other java that it runs, and I cannot find a JRE to check its version, so I'm not sure about that from a luminis product standpoint.
Calendar server requires the replacement of a timezone file. The info and file is on Sun's site.
Oracle DB. There are specific oracle patches that are recommended by oracle.
On Windows 2000:
Since our LMG 3.1 requires java 1.4x and the cygwin invoked LMB requires 1.3x, we have two JRE's running. One 1.3x in cygwin for LMB and one in the windows system environment running 1.4 for the LMG 3.1 startevents.bat to use. Both those java versions I upgraded to the ones recommended by sun.
The windows 2000 server itself required manual registry edits to be DST compliant. That information is listed on Microsoft's site. 2003 servers get automatic windows updates I believe.
-----
Would luminis run fine without every piece being 100% DST compliant? Probably. But I didn't research that aspect. I found it easier to just make all the operating systems, JREs, and applications like calendar compliant.
Events off an hour?
We're running 3.3.3.16 on Windows 2000.
My sysadmin used a TZupdater to update our test box last night, our Oracle dba has been applying Oracle patches, and I switched out the timezones.ics file . All events in the calendar prior to March 11 seem to have been moved to an hour earlier (e.g. 10-11 a.m. meetings are on the calendar for 9-10 a.m.) and everything after March 11 is listed at the correct times. When I replace the timezones.ics file with the old version of that file, I get the same results except the hour bump happens April 1 instead of March 11 for recurring calendar events.
If I enter a new 10:00 a.m. event for today, and it recurs past March 11, the time stays the same: 10 a.m. before and after March 11. In other words the problem only seem to happen for events that were already in the calendar.
Has anyone else had similar results? Surely this isn't the way it's supposed to work?
Did the sysadmin also update
Did the sysadmin also update the win2k box with the recommended microsoft fixes?
Calendar events off by one hour
I must admit, I'm confused as well.
We installed the timezones.ics and everything was fine, until our sysadmins installed the Solaris DST patches.
Then existing and new events in the 3-week window between the old and new DST start (last 3 weeks of March) were forward 1 hour.
I restored the original timezones.ics file and now all events appear correct.
I'm not sure what's happening.
It's as if the timezones.ics file makes up for a wrong time from the OS, but if you fix the OS you don't need the new timezones.ics file?? Not sure if this makes sense.
Bob.
Has anyone done synch data calendar?
We had a massive 4-hour difference on our calendar when I took over Luminis here ... eventually we fixed the timezone files customised for our Canadian timezone and had to run 'cptool synch data calendar' to update all the calendar objects. Once that was done, things were great.
Also, if you're on Luminis III.2, the command will run to a point and say something along the lines of:
02-28-07 17:18:51: Total objects processed: 34055
waiting for thread ... to terminate
This actually means it's done, apparently it's fixed in III.3.3 but we're not there yet.
I will be testing this later today, so hopefully by tonight or tomorrow I'll know better if that's the case.
Kent
DST
That does seem like thats how its supposed to work.. My question is that what if i just do it manually on march11th? Would it make a difference if i did it that way or do i have to change the .ics file?
I'll try this out on our
I'll try this out on our test boxes on Monday and see what happens. That is odd.
Got the same problem
We also saw the events scheduled between 3/12/2007 and April 1 shift one hour when we replaced the timezones.ics file. Going to open an incident with support. Luminis III.3.3 Build 64 on Win2K
Anyone else figure out how to deal with this?
John
As far as Sun is concerned,
As far as Sun is concerned, apparently, replacing the timezones.ics file will shift any pre-existing events between March 11th and April 1st. The only remedy is to fix those events.
I've called SCT, and there really isn't any way to avoid this... grr. Our campus employees largely use outlook on their desktops, so our helpdesk will probably issue a notice about how to fix that time period of events using the sync tool (export outlook calendar to file, delete outlook calendar, sync empty calendar with portal to empty it, reimport outlook calendar file, sync with portal again to 'fix' events).
Once the timezones.ics file is in place, any events created, even between march 11 and april 1st will be correct.