![]() GregorianCalendar returns bad WEEK_OF_YEARĮscalation: broken for time zone issue with date on windows JRE/Browser crash during repaint - IE/XP on MP or HT systems. RFE: Stall allocation requests while heap is full and GC locker is held Server VM crashes with -Xcomp in 1.4.2_05Ĭrashes at Function name=JVM_GetCPFieldSignatureUTF in jdk 1.3.1_13Įxception message's size is more than doubled everytime an exception is thrown REGRESSION: hotspot c2 crash running rmi JCK tests Important Note: You must restart the VM during January, 2007, in order to get correct the correct Daylight Saving Time rules after that date.īug fixes are listed in the following table. This release contains a fix for bug 6391777, supporting the new transition date. The transition to Standard Time will occur at 3 A.M. Because of this event, several Australian states will postpone the end of Daylight Saving Time from Mato April 2, 2006. The official version number for this update release is 1.3.1_18-b01.Īustralian Daylight Saving Time Fix: Melbourne, Australia, is hosting the Commonwealth Games during the month of March, 2006. Syntax used when invoking coreutils does not conform to POSIX 1003.1-2001 HttpURLConnection.disconnect doesn?t really do the jobġ.3.1_16 uninstaller removing TreatAs key for 1.5.0_02 OutOfMemoryError with Object allocation in JDK1.3.1_09 Long Integer value changes in unpredictable manner with Deoptimization(1.3.1_06) JVM 1.3.1 crash due to fatal error in exception handler Other bug fixes are listed in the following table. Otherwise, the codebase will be ignored by the class loader when restoring a Java object, and only those class files that appear on the classpath will be recognized. Instead, a new system property called .ustURLCodebase must explicitly be set to the string value true in order for a codebase to be used. Later, when restoring the original object, its codebase along with additional object data is retrieved from the directory and used by the class loader.Īn object's codebase is no longer implicitly trusted. When storing a Java object in an LDAP directory, the location of the object's class file (its codebase) may be specified. The behavior of the JNDI feature to store and retrieve Java objects in an LDAP directory has been slightly modified. Java Naming and Directory Interface (JNDI) API Change For more information, refer to Timezone Data Versions in the JRE Software. This release contains Olson time zone data version 2009a. The official version number for this update release is 1.3.1_25-b02. This release contains Olson time zone data version 2010b. The official version number for this update release is 1.3.1_28-b04. For more information, please see Oracle Java SE and Java for Business Critical Patch Update advisory. This release contains fixes for security vulnerabilities. This release contains Olson time zone data version 2010l. The official version number for this update release is 1.3.1_29-b03. Bug Database enables you to file your own bug reports, add comments to existing bug reports, and vote for the bugs you consider most important. To determine the version of your JDK software, use the following command:īug Database - In most cases, the bug ID number in each description below is a link to the detailed bug report on the Bug Database (Bug Parade) web site. The version numbers are given below, complete with build number. Update releases are bug fix releases and as such are not intended to add to or delete functionality in the original 1.3.1 release. This document summarizes changes made in all the 1.3.1 update releases, including a link to the original 1.3.1 release notes. Microsoft Windows, Linux, and Solaris Operating Systems
0 Comments
Leave a Reply. |