SDK/RTE 1.4.2.28 Release Notes

Table Of Contents
The file /etc/dld.sl.conf is only referenced when the application is executing
within an suid environment.
On IPF, starting with JDK 1.4.2.10, users can launch java from an suid application with
linker patch PHSS_32765 (or superceding patch) installed on the system.
With JDK 1.4.2.10 and patch PHSS_32765, users do not need to specify the JRE path in
/etc/dld.sl.conf.
HP Integrity (Itanium) Known Issues
Using pthread_suspend() under certain conditions on HP-UX 11.31 (11i v3)
For all Java versions running on HP-UX 11.31, if either of the following conditions is
true for a threaded application that uses pthread_suspend(), which is not
POSIX-compliant, setting the environment variable PTHREAD_SUSPEND_SYNC to
1 is strongly recommended. Failing to do so, can lead to undefined behavior:
The PTHREAD_FORCE_SCOPE_SYSTEM or PTHREAD_COMPAT_MODE
environment variable is set to either 1 or on.
The application's binary is brought forward from an HP-UX 11i v1 release.
Initializing a JVM instance with JNI_CreateJavaVM or attaching to JVM with
AttachCurrentThread()
Starting in 1.4.2.00 with the 64-bit SDK, the stack size required to initialize a JVM
instance with JNI_CreateJavaVM or to attach to JVM with
AttachCurrentThread() is greater than the HP-UX 11.23 (11i v2) Itanium pthread
default of 256K. If you wish to call JNI_CreateJavaVM or AttachCurrentThread()
from a pthread, you need to create the pthread with a larger stack size, at least 416K.
Stack overflow failures during JVM initialization are not always clearly reported as
such, since the JVM may not have yet installed its handlers, and the failures may appear
as random exceptions. The solution is to make sure you have enough stack space.
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. The defect does not exist on PA-RISC 32-bit systems.
Running Java with setuid or setgid
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.
Now it is allowed, but patches must be installed, the SHLIB_PATH and
LD_LIBRARY_PATH environment variables must be set, and a configuration file must
be set up.
24