Daylight Savings Time fix and CFDOCUMENT

After our webmaster installed the JVM update (1.4.2_13) to
correct the DST issue, I discovered that CFDOCUMENT doesn't seem to
function. Has anyone else ran into this issue?

We loaded 1.4.2_11 (as recommended in the technotes) and
cfdocument works okay, but we are getting random times when it
completely locks up the machine and crashes JRun. I believe there
is a bug that was introduced with the 7.0.2 updater and that jvm
that now affects cfdocument.

Similar Messages

Daylight Savings Time: Calendar and Outlook 2007 ...

Anyone else (particularly in Australia) having issues with their phone calendar being an hour out to their Outlook since DST came in on 5 October??
I have an N73 and Outlook 2007.

Here's the response I received from Nokia (haven't tried it yet but I do know GMT +11 is Vladivostok):
Hope you are in good health.
Kindly refer to the steps below to help resolve your issue:
1) Menu > Tools > Settings > General > Date & Time > Network Operator Time > Auto Update > Off
2) Menu > Tools > Settings > General > Date & Time > Time Zone > GMT +11
3) Manually change the time on your phone
4) Check each calendar appointments are showing the correct time. If they are not, please change the entries to the correct time.
5) Back up your phone using "Content Copier" on Nokia PC Suite
6) Perform a software update using Nokia Software Updater. Kindly visit the following link to obtain the necessary information on how to do a software update for your phone:
http://www.nokia-asia.com/A4707376
7) Synchronize the appointments from your PC to the phone. It is also best to check the "Conflict Resolution" settings in the Synchronize feature of Nokia PC Suite. This can be done by going to:
Nokia PC Suite > Synchronize > Settings > (select the arrow icon pointing to the right until you reach the "Finish" screen) > (select the wrench icon to proceed to the "Advanced Settings") > Conflict Resolution (choose which the priority location of information is)
The "Conflict Resolution" setting determines which information will be of priority, whereby the information on this location will override the information on the other location.
8) Check the time of the appointments on your phone if they are showing the correct time
I apologize for the inconvenience caused and hope the above helps to clarify your query.
Thank you for emailing Nokia Careline.
Should you still have any difficulties or any other enquiries, do not hesitate to write to us again or contact Nokia Careline at 1300 366 733. We operate between the hours of 8:00am and 8:00pm EST, seven days a week.
Do you know you can now update your phone software at your own convenience? Visit www.nokia.com.au/support to check if your phone model is supported and download the "Nokia Software Updater".
Have a wonderful day ahead!
Kind regards,
Naz
Nokia Careline

Daylight Savings Time 2007 and Jrockit JVM 1.4.2_04

If I have applications running on WLS 8.1 SP2 with Jrockit JVM 1.4.2_04 on AS3, would the NEW Energy act of 2007 which resets the DST in march insteadt of April affect my JVM? If yes is there a patch?

This fix is included in JRockit release R27.1 1.4.2_12 publically available from the download site.
Read more: http://java.sun.com/developer/technicalArticles/Intl/USDST/
BEA JRockit ports and includes the JDK from the Sun Java distribution, so things fixed in a Sun JDK is fixed in the corresponding BEA JDK.
Kind regards, Cecilia
BEA JRockit
Kind regards,
Cecilia Borg
BEA WebLogic JRockit

Daylight Savings Time and Time Zone Issue:

Howdy! Many of us woke up this morning to be dismayed to find that our iPhone was TWO hours behind instead of falling back one for the Daylight Savings Time adjustment, and were late for church. I have an iPhone 4S, with iOS 5...
I was working at that time of morning, and the initial switch went well. However, when I woke up, the clock was yet another hour behind. A little investigation showed that the Time zone had been changed to Denver (It was previously on Chicaco, and I live in Dallas.) I tried to select it to change it, and it wouldn't allow me. If I turned off the Set Automatically feature, then I could change it, but when I turned the Set Automatically feature back on, it would re-set the time zone to Denver.
I found another thread where they discuss this:
https://discussions.apple.com/message/16644669
To fix this, put in airplane mode, then back out again, then re-choose your correct time zone. If this doesn't work, then try turning your phone completely off and then on again. Thanks to 4n6doc for the tip!
The airplane mode trick worked for me: I turned airplane mode on, then off, then went to the Date & Time and set my time zone to Dallas, TX while the Set Automatically was off. When I turned the Set Automatically back on, it changed Dallas to Chicago, which is what every iPhone iOS I've ever had has done.

Hi,
Yes this is a correct way to fix the issue. One thing however, how did you set the timezone? For correct daylight saving handling, you'll have to use the long version, like America/New Yorw, NOT GMT-5 (for example).
regards,
~ Simon

Daylight Savings Time and Alarmsk

Since the daylight savings time updated over the weekend the alarms I had programmed on my iPhone will not set properly. The phone displays the correct current time so I know the clock has updated but any alarms I have set for the hour of 2am - 3am don't display the proper time. They keep reverting to 1-2am. I have deleted them and recreated them with the same results, on 2 different iPhones, a 4gig and an 8gig.

I see im not the only one that gets up early. v1.1.3 and updated to 1.1.4 I am unable to set the alarm to any time in 2AM (2:01, 3, 4, 5, etc..) any time set to 2AM shows 1AM in the alarm. 2PM shows fine. Any hour of the day shows fine. The error is setting a time of 2AM as it will not show that time and will revert to 1AM.
I am in a zone that uses DST.
I guess apple doesnt want us to wake up to pay the bills.
I hope someone has a fix for this before I goto bed... busting out the old alarm clock now.

Has anyone had problems in v5.0a of Iplanet calendar installed on a Sun box with creating events and daylight savings time?

Events created around 4/6/2002 at 8pm get created with the wrong time (9pm) and there are several other creation and display problems tied to Daylight Savings in April and October. Version 5.1 of the software seems to fix that but we are looking for a fix until we can upgrade. We have been using Windows systems to access the calendar.
Thanks.

We have not seen exactly this, but many users appointments are lining up in the wrong time slots. Also, when scheduling, the time display is off by an hour. We have found what looks like a temporary fix.
We noticed that the problem only affects users who have the start of the week set to Sunday (when daylight savings time started). Setting the week to start on Monday fixed our display problems (you can do it in the users, options section).
I am placing a support call w/SUN.

E-Load/e-ME and Daylight Savings Time Change

If you are using e-TEST suite versions 8.10 or older, please see the following knowledge base article on updating your JRE for e-Load and e-Manager Enterprise.
http://qazone.empirix.com/entry.jspa?externalID=201&categoryID=15
(you must be logged into QAZone to view this link)
It is recommended that e-Load and e-Manager Enterprise customers update the JRE on their e-Load and e-ME server machines using the SUN JRE patch referenced in the article.
e-TEST suite version 8.20 which is releasing this week does not require any update.
Message was edited by: jfernandes

My problem is that now CFMX 6.1 thinks that it is 8 hours
later in the day
than it really is (it is stuck on GMT now) and I am unable to
get CFMX to
acknowledge the operating systems clock. :-(
"GregK" <[email protected]> wrote in message
news:eord35$5mq$[email protected]..
The technote for this issue:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=d2ab4470
has
another
link to a technote which addresses null pointer exceptions
after upgrading
the
JVM on CFMX 6.1 systems:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=kb400232
The hotfix
described in that technote gives a fix for CFLDAP and
CFSERVLET tags after
the
new JVM is installed.
The important thing to note is that Adobe feels that
daylight savings time
will indeed present a problem for ColdFusion applications.
Unfortunately,
the
problems are not explained in any detail. I can guess that
functions like
DateDiff( ) may calculate incorrect values when spanning the
changed weeks
of
daylight savings time. As others have suggested; however,
simply retrieving
the system time, i.e. Now( ) function may not be affected as
long as the
operating system clock is set correctly.
Hope that helps.

CF MX and Daylight Savings Time Change

Next year 2007, the Daylight Saving day (chaning the clocks
for spring and fall) will be changing. The Spring date will be a
month earlier and the fall date a month later then it has been for
years.
How will the Cold Fusion Server for MX 7+ handle this? Will
it use the server time or use the internal CF Server clock?
Thanks.

My problem is that now CFMX 6.1 thinks that it is 8 hours
later in the day
than it really is (it is stuck on GMT now) and I am unable to
get CFMX to
acknowledge the operating systems clock. :-(
"GregK" <[email protected]> wrote in message
news:eord35$5mq$[email protected]..
The technote for this issue:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=d2ab4470
has
another
link to a technote which addresses null pointer exceptions
after upgrading
the
JVM on CFMX 6.1 systems:
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=kb400232
The hotfix
described in that technote gives a fix for CFLDAP and
CFSERVLET tags after
the
new JVM is installed.
The important thing to note is that Adobe feels that
daylight savings time
will indeed present a problem for ColdFusion applications.
Unfortunately,
the
problems are not explained in any detail. I can guess that
functions like
DateDiff( ) may calculate incorrect values when spanning the
changed weeks
of
daylight savings time. As others have suggested; however,
simply retrieving
the system time, i.e. Now( ) function may not be affected as
long as the
operating system clock is set correctly.
Hope that helps.

COREid and Daylight Savings Time for 2007

Do COREid or any of its components require any special fix in order to comply or function properly with the new Daylight Savings Time for 2007?
Background:
In August of 2005 the United States Congress passed the Energy Policy Act,
which changes the dates of both the start and end of daylight saving time
(DST). When this law goes into effect in 2007, DST will start three weeks
earlier (2:00 A.M. on the second Sunday in March) and will end one week later
(2:00 A.M. on the first Sunday in November) than what had traditionally
occurred.
Thanks,
Craig
Message was edited by:
user557097

We have experienced many problems with DST and COREid in the past; most of them resulting in hung Access server and unavailability. I don't know if it's because we have components distributed across multiple time zones or what. Our plan is to have someone available at the time change to cycle the services (and maybe the server as a whole) and do a health check after the fact. I hope this helps.
--Aaron

HOw do I fix the fact that ical jumped (almost) all my events post daylight savings time change an hour ahead?

A few weeks ago I noticed that everything past 3/8 was an hour ahead, and I assumed once daylight savings time changed it would all jump back. It hasn't, and I don't know how to continue scheduling events or if I should change them all. I read that (a few years ago) the suggestion was give it 24 hours to adjust??

I think this problem is more complex. Background - UK clocks went back at the end of October; the USA went back one week later. I am in the UK and my Outlook calendar contains appointments created in the USA.
Someone in the USA created a recurring appointment before any clocks went back. In Outlook everything is correct. The meeting times are the same each week except for the one week between the two clock changes when, quite correctly, the meeting shows up one hour earlier. When I sync with my iPhone, the meeting shows at the same time every week regardless - this is incorrect.
Someone in the USA created a recurring appointment in the week after the UK clocks went back but before the USA clocks did. Outlook correctly shows the first occurrence as one hour earlier than all the following occurrences. Unfortunately - and this is the really nasty bit - the iPhone shows ALL the appointments one hour earlier than they should be. The only one that is correct is the first one.
This is a nasty bug and something that Apple needs to fix.

Daylight Savings Time and Calendar?

What will happen to my iPhone calendar events come daylight savings time?

I have had that problem on my mac and iPhone. In my calendar it shows one hour later and even on my alarm clock app it is changing times, just odd random things.
On my iPhone I changed the time setting and it did not help. I am avoiding doing a total wipe and restore or whatever, because I don't want to go through the hassle of re doing everything.
I keep fixing my calendar and it keeps giving me trouble. Let me know if anybody has any ideas.

All-day calendar entries and daylight savings time

Since changing to daylight savings time, whenever I change the date on an all-day calendar entry, my iPad (but not my iPhone) changes the one-day calendar entry to a two-da calendar entry. How do I correct this?

Dates are represented internally with a long that represents the number of milliseconds past some fixed point. Timezones do not affect this.
I'm assuming you're getting your dates as java.sql.Date
You should then build a Calendar (see GregorianCalendar) and call setTimeZone() with your timezone without daylight savings

Appointments one hour ahead of appointments created in iCloud - both before *and* after the shift from daylight savings time

I am in the CET timezone and my Lumia 925 on 8.1 has consistently shown appointments one hour ahead of appointments created in iCloud - both before and after the shift from daylight savings time here.
My disappointment is compounded by the fact that I patiently waited for October, naïvely thinking the clockchange would solve things... doh.
Look forward to your earliest solution.
Jonny.

There is a separate thread on this subject. It's a bug in Windows Phone 8.1. It is fixed in the upcoming Windows 8.1 Update 1 release (due Nov/Dec 2014). Alternatively, you can install the developer preview (go to Store and search for 'preview for developers'.
You have to register as a developer though (easily done through appstudio.windows.com) or you can wait for your phone vendor (Microsoft / Nokia) to release the 'Denim' upgrade.
For now, I don't know a decent workaround.

ICal and iCloud Calendar Appointments Problems Following Daylight Savings Time Change

This morning following the daylight savings time change, I noticed that some but not all of my appointments had shifted forward an hour. Strangely enough, some are correct on the iCloud calendar but are still not correct in iCal. Is anyone else experiencing this problem? Here's another anomaly: the info panel is showing the correct time while the calendar view is not! I have turned off time zone support in both iCal and the iCloud calendar. It's so frustrating when you rely on these tools--especially for appointments--and you find that you can't trust them to be accurate!

samdale67,
Have you had any luck fixing this problem yet?
I just noticed today that my iCloud calendar is consistently one hour behind my iPhone4s calendar. It's as if my iCloud calendar never got the Daylight Savings Time Spring Forward message. The iPhone, on the other hand, updated to DST right on schedule. It's annoying because I'm starting to use my iCloud calendar and would like the time change to be applied.
DaveStump

IdM Scheduler and Time Change to Daylight Savings Time GMT to BST

This isn't really a 'question' , but just a topic for discussion.
We're not live yet, but will be by the time the clocks go back. So I'm just interest to hear everyone's experiences and any issues with regards to the switching to / from DST
I did some "interesting" (or not) tests last night to see what happens with Pending Values which are due to take effect at the time change threshold of 01:00 GMT when switching to Daylight Savings Time (BST) GMT +0100.
It seems as if the IdM scheduler keeps going according to UTC or GMT. However any values provisioned to target systems or to local tables using the ddm.datetime8601 system variable are in local time according to the runtime server or SQL server's locale settings.
I set up a task to output from a javascript the current system date
using the following in the functions.
currentTime = new Date();
return currentTime.toString(); // returns Locale Time String
currentTime = new Date();
return currentTime.toUTCString(); // returns UTC Time String
in the same pass I also output the ddm.datetime8601 system parameter and the ddm.time24 system parameter.
This task was to update a comment on an entry and Scheduled to run at 00:00:00 and was executed at 00:00:06 GMT all times were still in GMT as expected.
Local Time: Sun Mar 27 00:00:06 GMT-0000 (GMT) 2011, UTC Time: Sun, 27 Mar 2011 00:00:06 GMT, ddm.datetime8601: 2011-03-27T00:00:06, ddm.time24: 00:00:06
This task was scheduled at 01:00:00 in IdM and was exectued at 01:00:08 GMT by the runtime, and you can see the local time is being correctly reported as 02:00:08 BST. Note also the ddmdatetime8061 is also 02:00:08 i.e. BST.
Local Time: Sun Mar 27 02:00:08 GMT+0100 (BST) 2011, UTC Time: Sun, 27 Mar 2011 01:00:08 GMT, ddm.datetime8601: 2011-03-27T02:00:08, ddm.time24: 02:00:08
In the database the entry values MXI_VALUES ModifyTime field has the GMT / UTC timestamp.
I also set up some pending value objects to be applied at 00:59:59 and 01:30:00 to see if the 01:30:00 would be 'skipped' as the locl clock change would've gone from 00:59:59 to 02:00:00. Well the pending values were correctly applied and expired and no 'lost' transactions happened as a result of the change.
So essentially it seems to me that the IdM runtime and scheduler times are all based on UTC / GMT.
I guess it's only an issue twice a year if you're expecting something to happen at a specific local time 01:00:00 or if you've got a global user base and their account expiry should be in each user's own country's local time. In these cases, it would seem that you'd need to convert the schedule times and pending value times to UTC first before setting them in the database.
Has anyone else had any issues, thoughts, questions or suggestioins on scheduling tasks which span the DST time change when switching to and from Daylight Savings Time.
Edited by: Paul Abrahamson on Mar 27, 2011 10:51 AM

Read here:
http://www.appleinsider.com/articles/10/10/11/applesays_ios_software_update_to_fix_pesky_alarm_clockbug.html

Daylight Savings Time fix and CFDOCUMENT

Similar Messages

Maybe you are looking for