Release Notes
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This document contains important details for this version of BEA JRockit 1.4.2 SDK. It contains information on the following subjects:
The BEA JRockit 1.4.2 SDK is subject to the terms and conditions of the BEA JRockit Binary License Agreement.
This release is certified on the platforms listed on the Supported Platforms page.
BEA JRockit 1.4.2 SDK is available as part of the WebLogic Platform 8.1 suite (Service Pack 3 and higher) and as a standalone application. For instructions on installing the standalone JRockit application, please see Installing BEA JRockit 1.4.2.
This version of the BEA JRockit SDK includes the BEA JRockit JVM Version R24.5.0 compliant with Java 2 Platform, Standard Edition, v 1.4.2_08. This is represented by the BEA JRockit version number 1.4.2_08 R24.5.0.
This release of BEA JRockit SDK includes a complete documentation set comprised of these documents:
Additionally, the following web-only documents are available:
Copies of all BEA JRockit 1.4.2 SDK documents can be found at:
http://edocs.bea.com/wljrockit/docs142/index.html
For details on these new features and other features, please refer to New Features in BEA JRockit 1.4.2 SDK in Introduction to BEA JRockit 1.4.2 SDK.
This section describes the most recent changes of BEA JRockit.
Table 1 lists the changes have been made for this release.
Property differences between BEA JRockit and Sun Hotspot have been eliminated. See System Property Changes for a list and description of these changes. |
|
With earlier versions of BEA JRockit, you were unable to use multiple |
|
Calling |
|
The implementation of the mmap syscall on RedHat Enterprise Linux 3.0 was mapping the lowest page in the virtual address space (starting at 0x00000000), breaking anything trying to access to this page to generate a SIGSEGV; for example JRockit null pointer exceptions or a forced dumping. This issue hs been resolved by marking the null pointer memory area inaccessible before it can be compromised. |
|
JRockit crashes when calling |
|
When specifying |
|
When BEA JRockit crashed when running on an IA64 Linux 2.6-based systems, the stack trace that printed in the crash dump would be incomplete. The product has been corrrected so that the stack trace is now complete. |
|
When running WLS 81 SP2 and JRockit with OptimizeIt's Code Coverage, null pointer exceptions were thrown in the security providers. This has now been fixed. |
|
Applications that over-allocate direct NIO buffers (e.g. A new option, |
|
|
|
A variable memory leak in gencon garbage collector has been fixed. |
|
FileInputStream.skip with relative negative offset now valid. |
|
When running with |
|
When BEA JRockit crashed when running on a Linux 2.6-based system, crash dumps were cut off whenever the crash dumping code tried to read from read-protected memory. The crash dumping code can now handle read-protected memory and is more likely to produce complete crash dumps. |
|
|
|
WLS 8.1 SP3 - Jrockit crashes when calling |
|
BEA JRockit no longer fails to start on Windows 2003 SP1 on Itanium. |
|
|
|
Some customers, when trying to start their server would occasionally experience server hang-ups during the code generation phase of startup. This issue has been resolved by employing a reprocess to pre-resolve classes before code generation. |
|
Running the Memory Leak tool did not display "points-to" information when using the singlecon garbage collector. This has been fixed. |
|
JNI frames were faulty for methods that either returned an object or were synchronized. This has now been fixed. |
|
There was a crash in the garbage collector (mmGetObjectSize) that has been fixed. |
|
Conversions to Strings given byteArrays greather than 16Mb gives |
|
Some customers, when running BEA JRockit 1.4.2_04 with a high load on Linux AS 3.0 using native threads and a parallel garbage collector would encounter socket exceptions. These exceptions corrected in this service pack by adding a missing synchronization to socket read/writes. |
|
More |
|
The |
|
When trying to run WebLogic Server and 15,000 jsp pages on BEA JRockit, a customer was running out of native memory. This issue was resolved. |
|
JRockit now prevents that someone alters the parent field in |
|
BEA JRockit was crashing when an internal ZipFileP, despite being freed upon zip closing, was still referenced and used by ZipInputStream. This issue was resolved by ensuring that the input stream no longer holds native data. |
|
Application program no longer gets |
|
Dumping behavior has been improved to better ensure that a crash file is generated whenever a crash occurs. |
|
Changed all references from BEA Weblogic JRockit(R) to BEA JRockit(R). (See also System Property Changes.) |
|
Accessing a non-NULL Java array with index value of 0 no longer gives a |
|
Changes to |
|
JRockit no longer accepts shortened versions of command line switches. |
|
A crash in caFPUPushExtendedDouble in linux environments is fixed. |
|
A rare error when using apache-xalan xml/xslt transforms is fixed. Xalan uses the swap bytecode (seldom used by javac) which triggered bad behaviour within BEA JRockit. The issue was tracked here as well: http://issues.apache.org/jira/browse/XALANJ-1778 |
|
JRockit no longer crashes on zip-files with unusual extra data. |
|
JRockit no longer core dumps on stack overflow on Windows 2003 SP1 on Itanium." |
|
An optimization recursion issue could cause stack overflow, e.g. crash dumps with a recursive call stack in |
|
ObjectStreamClass.lookup() could hang if a class explicitly defines its serial version UID in a static field and also looks up its serial version UID in its static initializer. SUN bug 4803747 fixed. |
|
With earlier versions of BEA JRockit that supported the JRockit Runtime Analyzer, if you had an expired |
|
JRockit can now be linked with C-programs that also make use of pthread_create. |
|
Certain options that were available in BEA JRockit 1.4.1 are not available in BEA JRockit 1.4.2. Please refer to Changes Between BEA JRockit 1.4.1 and 1.4.2 Releases for a list of these options. |
|
When synchronizing on a thread and trying to perform |
|
After some bounds checking, a |
|
Differences between the Sun JDK implementations of both the |
This section describes, by associated platform and Change Request, changes to system properties in this service pack. The purpose of these changes was to remove any differences between BEA JRockit system properties and those used by the Sun JDK.
This section describes changes to system properties which are valid on all platforms.
java.vm.vendor.url.bug = "http://support.bea.com";;
"http://support.bea.com";;
java.vm.name = "BEA JRockit(R) 1.4.2_08 JVM R24.5.0-46"
BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1"
BEA JRockit(R) 1.4.2_08 JVM R24.5.0-46"
Changes Based Upon CR223211 and CR203172
user.country
user.language**user.variant
file.encoding
file.encoding.pkg
This section lists and describes system property changes available only on Windows 32- and 64-bit platforms.
user.home
property"USERPROFILE"
"USERPROFILE"
user.name
property"USERNAME"
; fallback on system callThis version of BEA JRockit contains no Linux-specific system property changes.
Table 2 lists the changes made for BEA JRockit 1.4.2_05 R24.4.0.
Table 3 lists the changes made for BEA JRockit 1.4.2_04 R24.3.0.
The following options were supported in BEA JRockit 1.4.1 but not in BEA JRockit 1.4.2.
Xnativethreads
Xthinthreads
Xallocationtype
Xalloctype
XXcodecoverage
XXnonparallelgencon
XXjradelay
XXjrarecordingtime
XXjrafilename
XXjranonativesamples
XXfatlockreads
XXfatlockyields
XXfatlockspins
XXenablefatspin
XXspinsbeforeinflation
XXspinsbeforeyield
XXspinsbeforeread
XXspinsbeforeread
The following issues are known in the 1.4.2_05 and 1.4.2_08 release:
JRockit can't mmap more than 2GB on SuSE The Java heap is limited to approximately 2 GB on SUSE Linux 8 and 9. JRockit needs contiguous virtual memory for the Java Heap. These operating systems load libraries on the 1 GB boundary. |
|
Java stack traces are limited to 32 frames. This may make identifying the cause of a java.lang.StackOverflowError difficult. |
|
RHEL 2.1 cannot produce core files larger that 2 GB even though the process size may be up to 3 GB. Core files are created by the OS when JRockit dumps because of a bug in JRockit or in third-party JNI code. The core files are used by BEA support and engineering to find the reason of a crash. Therefore, BEA cannot support customers with a JRockit process size exceeding 2 GB. |
|
When starting WebLogic Server 8.1 SP5 as a Windows Service, with the bundled BEA JRockit 1.4.2_08 (R24.5.0), JRockit crashes during startup. Contact BEA Support for a patch. |
|
Some JVM options are case sensitive. This is particularly noteworthy since some non-standard options are written in a new form, for example, |
|
A signal being sent to wrong thread on Linux 2.6 kernels on Itanium (2.6.11 and previous Itanium kernels) might cause random hanging or crashing JVM. |
BEA JRockit is known to hang or crash on 2.6 kernels on Itanium, due to a bug in the Linux 2.6.11 (and previous) kernels. The bug is in the kernel We cannot estimate how often the bug actually occurs, but under different circumstances it has been seen as often as once per hour or as seldom as once every two days. BEA believes that this issue affects SMP systems more than single CPU systems. Affected Linux versions are: SuSE Linux Enterprise Server 9.0 and Red Hat Enterprise Linux 4.0 on Itanium running on 2.6.11 (or previous) kernels. (CR230226 and CR218035). SuSE has confirmed that this bug will be fixed in their upcoming SLES 9.0 SP2 release. We are working with Red Hat to get this fix into RHEL 4.0 Update 2. You can see the committed patch at:
Customers running SMP systems must patch their kernel to include the kernel fix or upgrade to a newer kernel. As of this writing (June 17, 2005) no officially updated kernels are available. If you are running on SLES 9.0 Itanium, you should upgrade to SP2 once it is made available. The Red Hat internal reference number is 74397. For SuSE the internal reference number is 78084. |
JRockit 1.4.2_05 R24.4.1 on Red Hat Enterprise Linux 4.0 x86_64 is suffering from Red Hat Enterprise Linux 4.0 kernel bugs. You must use the Red Hat Enterprise Linux 4.0 Update 1. |
|
When using the JRockit 1.4.2 on Linux, you should first make sure that the environment variable 'LD_ASSUME_KERNEL' is *not* defined. If 'LD_ASSUME_KERNEL' is defined, JRockit will use an older and slower threading implementation for no gain. |
|
Do NOT install i386 versions of glibc on Red Hat or SuSE Linux since JRockit will randomly crash or hang. JRockit only supports the glibc versions built for the i686 architecture on Red Hat IA-32. |
|
When running the Java BEA JRockit Management Console over a remote X connection, turn the anti-aliasing option off, since it severely slows down the console. |
|
When starting BEA JRockit with the |
|
When using Linux on Hyper Threading-enabled Intel processors, be aware of the following:
JRockit will still work on Hyper Threading enabled system even if it doesn't detect that Hyper Threading is enabled, but Hyper Threading specific optimizations will not be performed. |
|
Java Plug-in with Netscape 7.1 and Mozilla 1.5 on Linux requires different libgcc files. There are two different compilations of the Java Plug-in library for Netscape 6: one "normal" and one compiled with gcc 3.2. As noted in the Sun Java Plug-in installation guide for Linux at: http://java.sun.com/j2se/1.4.2/manual_install_linux.html#noteNewer browser versions, specifically Mozilla 1.5 and Netscape 7.1, require the gcc-3.2-compiled version of libjavaplugin.so in The newer ns610-gcc32 version requires the library libgcc_s.1.so, which is not installed by default on Red Hat Linux Advanced Server 2.1. Therefore, if you are going to use one of these browsers on Red Hat Linux Advanced Server 2.1, we recommend that you install Note: This is a non-standard library with the remote possibility of having an adverse effect on your system. |
|
JRockit might under some circumstances report the wrong line number in the stack trace of a thrown |
|
JRockit may deadlock when forking. This may occur when compiling JSPs. There is a known issue in Red Hat Advanced Server 2.1, see: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115429 for more information |
![]() |
![]() |
![]() |