JDK DST Time Change for 2007

I just got an e-mail from Sun about the DST issue for 2007.
Is Adobe going to come up with a fix for this or should we download
the JDK directly from Sun? We are currently running JDK 1.4.2_04.
Some sort of communication about this issue would be appreciated.
U.S. Daylight Saving Time Changes in 2007
The United States has planned a change to its DST observance
beginning in 2007. The Energy Policy Act of 2005 mandates that DST
will start on the second Sunday in March and end on the first
Sunday in November. In 2007, the start and stop dates will be March
11 and November 4, respectively. These dates are different from
previous DST start and stop dates. In 2006, the dates were the
first Sunday in April (April 2, 2006) and the last Sunday in
October (October 29, 2006).
If you are concerned about application failures that may
result from these DST changes, you should update your Java Runtime
Environment. The following Java platform versions have correct time
rules to handle the DST changes that will affect U.S. time zones in
2007. You can download any of the following Java platform versions
to resolve this DST issue:
JDK 6 Project (beta)
J2SE 5.0 Update 6 or later
J2SE 1.4.2_11 or later

Ok, I have figured out what the issue is here. I'm posting
this in the hopes
that Adobe will modify their document, "How to upgrade the
JVM that ships with
ColdFusion" at
http://www.adobe.com/go/2d547983.
There are several steps that
are omited or vague, so here is some additional information
that will help you
in the upgrade process.
JVM 1.5.x is NOT supported for ColdFusion. The link
specified for the upgrade
process points to the Java SE page which currently displays
1.5.x as the
current version. Instead go directly to the 1.4.2x page at
http://java.sun.com/j2se/1.4.2/download.html
to get the correct version of the
JVM.
It should also be noted that the default installation for
the JVM points to
C:\Program Files\Java\JDK<version>, this default
directory must be changed
because the java.config file does NOT allow for white space
in the java.home
argument. When installing the JVM you should choose the
?Custom? install and
install to C:\Java or a directory structure that does not
contain spaces. It
may be helpful to rename the JRE directory under Jrun4 and
install to that
directory directly if you don?t want the java files outside
of the Jrun
directory. This is important because if there is white space
in the directory
structure, ColdFusion will not start up and return a ?Service
fails to start
with Service-Specific Error 2? message when starting the
service.
Once you have installed the JVM it is necessary to create a
directory in the
JVM folder called ?Server?. There is already a directory in
the folder called
?Client?. Once you create the Server directory, copy the
contents of the Client
directory into the new directory called Server; this is
completely omitted from
the document and is important to the process for upgrading
the JVM.
Using the above information combined with the document
provided by Adobe, I
was able to install the JVM 1.4.2_11 and ColdFusion started
up using it.
Hopefully these suggestions will help others in the future
when they need to
upgrade the JVM.
Thanks!

Similar Messages

  • DST time change for global companies

    We are curious to hear how other companies are handling the DST time changes in spring and fall especially if they are global and operating in multiple time zones.
    Do you set servers to UTC/GMT?
    And set SAP systems to UTC?
    And let users set their local time zone?
    Would that mean we don't have to worry about the fall and spring time change any more because UTC doesn't change? (That would be nice!)
    TIA,
    Margie

    Hi Volker,
    these "right setting" makes me unconfident.
    note 7417 tells me that that better shut down the system because the majority of the applications are not certified for a continued operation
    note 102088 tells me how to minimize the downtime to one hour... these is the procedure we were using the last years
    note 950114 tells me how to avoid the double hour by using zdate/DSTswitch_contloctime (=on you need not to shut down the system)
    note 391658 tells me "If you are converting from summer time to winter time, shut down all SAP instances before the scheduled conversion (for example, at 01:30) and wait at least an hour before you restart them."
    Your experience to let the systems run was quite good, but it is dissapoints me that SAP does not give a distinct statement about the DST. As mentioned befor, it is not practicable to shut down the SAP system in a global environment.
    cu, Christian

  • Daylight Saving Time Changes for 2007

    Hello Friends
    Sun's J2SE 1.4.2_11 has taekn care of the new Daylight Saving Time changes in accordance with The Energy Policy Act of 2005. Does anyone know if bea has incorporated same changes to their Jrockit, if so then starting which version.
    http://java.sun.com/developer/technicalArticles/Intl/USDST/
    Thanks for the answers in advance.
    Regards
    Rajeev Bhogal

    Hello All
    We currently compile and run our application with Jrockit 1.4.2_04 (build 1.4.2_04-b05), if we change to minor version 11 for 1.4.2 should we recompile the application. I would think that DST related binaries would only be called at run time not compile time, however I am far from being a compiler expert. Can any learned friend shed some light.
    Henrik what do you think.
    Regards and Thanks
    Rajeev Bhogal

  • Daylight Savings Time Changes for 2007

    Could Oracle have made it any more confusing to update database server software for the DST changes starting in March? One document I read points to at least a dozen other documents, some of which are actually written in English.
    Has anyone been able to simplify this procedure or are you all just hoping the DST changes don't affect you?

    Are you not able to find the correct patch for your database platform?
    You can always contact Oracle Support to clarify any issues you may have that relate to your platform.

  • Daylight Saving Time Changes in 2007 for USA

    Can anyone give me solution how to handle Daylight saving Time changes in 2007 in USA for JDK 1.3.x releases? We are using this due to some vendor dependency. We can�t upgrade to higher versions up to middle of the 2007. I would be thankful if somebody gets back to me.

    I have a similar issue where we cannot upgrade the jdk 1.1 without involving a lot of effort. If we keep the same old jdk, can someone tell me if use of Date and Calendar api will be impacted by the Daylight saving change.....provided the timezone is default and not explicitly set to EST. Also there isnt any timezone related buss logic.

  • Time change for daylight savings and Alarms not working correctly

    we have 3 iPhones in our house. 2 were set to auto time change for daylight saving and one wasn't. 1 did the auto time change with out an issue and all alarms worked ok. The other 2 have had issues with not been able to set the alarms ie set alarm for 0630 and it goes off at 0530 even though the time is set correctly. The 1 that was set to autotime worked fine until I switch auto time off, now the alarms on this one wont work either. well they work but just at the wrong time. The 3rd phone will allow alarms to be set, but the alarm will go off an hour earlier and this phone will not allow the alarm to be set for 0630 at all.
    Has anyone had this issue and resolved it. It makes getting up for shift work a right pain..

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

  • My wifi network is 802.11n but there are times changing for 802.11g, and have to restart ... after the update for Mountain Lion

    My wifi network is 802.11n but there are times changing for 802.11g, and have to restart ... after the update for Mountain Lion...  Help!!!
    Several problems with Mountain Lion, APP STORE (login/logout error), WIFI(802.11n for 802.11g), MAIL (horrible)... Apple, what is happening?   

    Do a factory reset .. nothing will be deleted from your backups and you will be able to get access to them again.
    The Factory Reset Gen1-4.
    Unplug your TC. Hold in reset. and power the TC back on.. without releasing reset for about 10sec. When the status light flashes rapidly; release it.
    Be Gentle! Feel the switch click on. It has a positive feel..  add no more pressure after that.
    TC will reboot after a couple of minutes with default factory settings and will wipe out previous configurations.
    No files are deleted on the hard disk.. No reset of the TC deletes files.. to do that you use erase from the airport utility.

  • Support for US Daylight Saving Time changes in 2007

    The Start and Stop dates for Daylight Savings Time in US will change from 2007.
    From Sun's bug database, it looks like Sun has handled this Daylight Saving Time changes in JDK 1.5.0_06.
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6317178
    Does anyone know if they have handled this in earlier JDK releases (1.3.x, 1.4.x)? If not, do they have any plan to handle these changes?

    1.3.1_18 had a timezone change.
    http://java.sun.com/j2se/1.3/ReleaseNotes.html
    1.4.2_11 had some timezone changes (but now there is a 1.4.2_12, so use that).
    http://java.sun.com/j2se/1.4.2/ReleaseNotes.html
    Not sure exactly what the timezone changes were, but check the release notes or give those JDKs a try.

  • App. Servers Patches (Fix) for U.S. Daylight Saving Time Changes in 2007

    Hi --
    I am having an issue with Oracle 10g Application Server (9.2.0.4 and 10.1.2) and BEA Weblogic (8.1.4) upgrading their corresponding JDK's to resolve the Daylight Saving Time Changes. Right now these app servers are using SUN jdk version, whcih prone to the DST issue, less that JDK 1.4.2.11.
    The details about the DST can be found at this location:
    http://java.sun.com/developer/technicalArticles/Intl/USDST/
    Thanks

    Hi,
    Thanks for posting.
    Metalink Note:403311.1 for DST E-Business Suite (EBS))Patches.
    Regards,
    Phani.K

  • Oracle Fix for U.S. Daylight Saving Time Changes in 2007

    Hi --
    Does any one know that if Oracle 10g Application Server (9.0.4) or Oracle 10g Application Server (10.1.2) as a fix for this issue.
    Summary of the Issue: Information about the impact of the US Energy Policy Act of 2005, which changes the effective dates of US Daylight Saving Time (DST) in 2007 for the US. The passage of the Energy Policy Act of 2005 alters the Daylight Saving Time (DST) start and stop dates by four weeks. Extended Daylight Saving Time will begin in March of 2007.
    The details for the issue can found at this location:
    http://java.sun.com/developer/technicalArticles/Intl/USDST/
    Thanks

    Hi,
    Thanks for posting.
    Metalink Note:403311.1 for DST E-Business Suite (EBS))Patches.
    Regards,
    Phani.K

  • Daylight Savings Time Change Mar-2007

    Is this years new date for DayLight Savings Time going to affect my WRT54G v3.1 router?  My firmware is 4.30.5.
    Also, does anyone know why the opening admin page for my router say I have a WRT54GL?

    Versions 1 - 4 and GL's use the same firmware because they all have the Linux operating system.
    The new release firmware for versions 1 to 4 is 4.21.1  If there is no fix for the new DST in 4.30.x it might be in the new release.

  • Unwanted automatic time change for no reason

    I've got a 6021 that changes time by one or two hours for no apparent reason whether it's in automatic time adjust or not.
    The firmware version is 4.10 092005; has it been improved since then?
    CK

    Yes, current version is 04.90. A firmware upgrade should sort out the problem for you
    Best Regards
    Dave

  • Leap second time change for 2009

    A 'leap second' will be added onto the final minute of 2008, does anybody know if this impacts Oracle ?

    Oracle RDBMS needs no patches and has no problem with the leap second changes on OS level
    Please see the oracle Doc Id # 730795.1

  • U.S DST change in 2007

    I am using Java 1.3.1_02 in my application running on Solaris 8. I have been searching around to determine if there is a patch/upgrade available for this version of Java to handle the U.S DST time change in 2007.
    I could find info on an Australian summer time change handled in 1.3.1_18, but I am not sure if this fixes the U.S time change in 2007.
    I know there is a Solaris patch available, but is there a patch/upgrade from Sun for Java 1.3.1_02.

    Its quite the kludge, but here's what I did on the 2.5.1 box we have.
    I installed patch 103834-01. Its a timezone fix for Brazil or some such from 1997.
    It also includes the "newer" version of zic, which will actually compile the TZ files.
    I was then able to compile the new timezones just like I was able to on 2.6 and Sol7.
    Ugly? Yes. Workable? Absolutely.

  • 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

Maybe you are looking for