HP-UX 11i Java™ JDK/JRE Version 6.0.22 Release Notes

have yet installed its handlers, and the failures may appear as random exceptions. The
solution is make sure you have enough stack space.
Using compiler safepoints (HP-UX 11.11 (11i v1) PA-RISC)
Using compiler safepoints guarantees a more deterministic delay to stop all running Java
threads before doing an operation requiring a safepoint synchronization, such as a
garbage collection. The compiler safepoints feature is enabled by default beginning with
Java 5.0. It uses a newer implementation than in previous releases which requires no
HP-UX patches. It can be disabled with -XX:-UseCompilerSafepoints.
shl_load HotSpot libjvm problem due to TLS (HP-UX PA-RISC 32-bit only)
The libjvm library for the HotSpot 1.4 JVM uses thread local storage (TLS). Currently,
the dynamic loader that is used by shl_load does not support dynamically loading a
shared library containing TLS when the library was not included in the link line.
You may need to load a library dynamically (using shl_load or dlopen) that contains
TLS, such as libjvm.sl, without having linked your application against it. This might
be the case if your application uses plug-ins.
The current workaround is a new linker feature LD_PRELOAD_ONCE.
To obtain the LD_PRELOAD_ONCE functionality, you need to install the following patch
(or the patch that supersedes it):
HP-UX 11.11 systems, install patch PHSS_35385
HP-UX 11.23 PA systems do not need a patch
HP-UX 11.31 PA systems do not need a patch
For more information on LD_PRELOAD_ONCE functionality and its limitations, read the
manpage for dld.sl after you install the patch.
NOTE: In some cases, using LD_PRELOAD_ONCE with Java that uses the Java launcher
program instead of the previously used Java launcher script, signal chaining for the actual
Java program did not work as expected. If you experience this problem, we suggest you
use the new environment variable, JAVA_PRELOAD_ONCE. In the top level driver, the
value of JAVA_PRELOAD_ONCE is set to LD_PRELOAD_ONCE, so that the
LD_PRELOAD_ONCE is set for the actual executable instead of the driver.
Using linker option +noenvvar and +compat on HP Integrity and PA-64 systems
If your application links with libjvm and uses the JNI interface APIs to load the JVM
directly, do not use the linker options +noenvvar or +compat on HP Integrity or PA-64
systems.
Running Java with setuid or setgid on HP Integrity and PA-RISC
Running Java from setuid/setgid executables is restricted on HP-UX. In previous
HP-UX releases, executing Java from a setuid/setgid environment was not allowed.
Known issues 21