Release Notes
This document contains important details for BEA JRockit 5.0 (R25.2) JDK. It contains information on the following subjects:
The BEA JRockit 5.0 (R25.2) JDK is subject to the terms and conditions of the BEA JRockit Binary License Agreement.
BEA JRockit JDK is available as a standalone application. For instructions on installing BEA JRockit, please see Installing BEA JRockit JDK.
This release of BEA JRockit JDK includes a complete documentation set comprised of these documents:
Copies of all BEA JRockit documents can be found at:
http://download.oracle.com/docs/cd/E13188_01/jrockit/docs50/index.html
Below you find information about the most recent changes of BEA JRockit.
The following CRs have been corrected for this release.
The following CRs have been corrected for this release.
Below are new features, changes, and enhancements for each release listed.
-Xrs
(reduce signal use) has been added. This option tells the VM not to use any operating system signals for a lot of things, but instead rely on the loading application (the launcher) to handle TERM
, INT
; HUP
, and QUIT
. For Linux users: Unless run with -Xrs
the JVM will install handlers for SIGQUIT
, SIGTERM
, SIGINT
and SIGHUP
unless the loading process has set handlers for these to SIG_IGN
, thereby hinting that these signals should not be used at all. If a calling process sets the handler for SIGQUIT
to SIG_IGN
, it will, however, still be replaced by the VM handler unless run with -Xrs
.
-Xgcprio:throughput
is the default garbage collector.-Xpausetarget
has been added. This flag enables you to set a specific pausetime if you are using the dynamic garbage collector with pausetime argument. The default setting is 500ms.-Xverbose
can now be set with the arguments: opt
, mem
, gcpause
, and gcreport
.-XXusethreadpriorities
.
The following issues are known in the BEA JRockit 5.0 release:
Australian Daylight Savings Time change for 2006 not supported. |
This release does not contain a fix for the Australian Daylight Savings Time change for 2006. Please contact BEA Support for a patch. |
JRockit crashes when using a heap larger than 5375 MB on Red Hat 4.0 for EM64T/AMD64. |
You can workaround this problem by using a heap smaller than 5375 MB. |
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 RedHat 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 RedHat 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. At the time of our release (June 22, 2005) no offically updated kernels are available. If you are running on SLES 9.0 Itanium, you should upgrade to SP2 once it is made available. The RedHat internal reference number is 74397. For SuSE the internal reference number is 78084. |
BEA JRockit Memory Leak Detector hangs when displaying aquired instances. |
The BEA JRockit Memory Leak Detector could in some instances cause JRockit to freeze or crash. (CR228592) |
JRockit deadlock on SUSE Linux Enterprise Server 9.0 running on x64/SMP |
There is a kernel bug in SUSE Linux Enterprise Server 9.0 x64 version, which causes signals to be lost on rare occations on multi-CPU systems. This is not noticable for most applications, but JRockit relies heavily on signalling, and is therefore affected by this bug. The consequence of the bug is that JRockit deadlocks. For this reason, it is *not recommended* to use JRockit for production on this platform, until this problem has been fixed by SUSE. BEA is working with SUSE to get the fix into the kernel. Affected Linux version is SUSE Linux Enterprise Server 9.0 SP1. The problem is also present in RedHat Enterprise Linux 4.0 GA on x64, but it will be fixed in the upcoming RHEL 4.0 QU1. (CR230225 CR220658) |
JRockit may crash with an Illegal memory access and point to a problem in mmNurseryAddTLAsToCache. This is a timing dependent problem that might occur when run with a generational garbage collector. Low probability (CR229720). |
|
Under certain circumstances, JRockit can crash when unloading classes (CR229723). |
|
If JRockit has been installed as a java plugin for a browser, pressing "v" (dump threads) in the Java Console has a high chance of causing JRockit to deadlock (CR225442) |
|
This is because line numbers are not available for the classes in the |
|
When running Workaround: set an explicit |
|
Using dynamic code replace from a debugger will cause static field values to be reset to zero/null, and can also cause spurious crashes at a later time due to un-updated references to the old field values. Workaround: do not redefine class definitions containing static fields |
|
If you are using JRockit in conjunction with a native library that relies on OS signals you may experience crashes due to a signal handling conflict between JRockit and the native library. Workaround: set the environment variable
BEA Engineering found this conflict using IBM's MQSeries native drivers, and it may be present in other libraries that rely on native code. For more information, see http://java.sun.com/j2se/1.5.0/docs/guide/vm/signal-chaining.html |