SDK/RTE 1.4.2.28 Release Notes
Table Of Contents
- Table of Contents
- Overview
- Features
- Installation
- Usage Documentation
- Removing support for unwanted architectures in the JRE
- Support for dynamic thread local storage (TLS)
- Signal Chaining Functionality
- Support for C++ applications built with -AA and -AP options (PA-RISC) only
- Using Java 2 JNI on HP-UX
- HotSpot JVM Options
- Garbage collectors: Parallel, Concurrent mark, and Sweep
- Allocating physical memory and swap in the Java heap
- Asian TrueType fonts and Asian locales
- Date/Time methods defaults
- Profiling
- Closing a socket when accept or read is pending (PA-RISC) - new patch information!
- Compatibility with previous releases
- Runtime Plug-In usage and configuration
- GC log-rotation support
- ThreadDumpPath support
- Additional HP and Oracle Java documentation
- Problem Fixes
- PA-RISC Known issues
- Recommend setting PTHREAD_SUSPEND_SYNC to 1 under certain conditions (HP-UX 11.31 (11i v3))
- shl_load HotSpot libjvm problem due to TLS (HP-UX 11.0 PA-RISC)
- 64-bit Support X/Motif (HP-UX 11.00 & 11.11 (11i v1) PA-RISC)
- 64-bit Support - System Call (HP-UX 11.00 PA-RISC)
- /dev/poll Runtime Support (HP-UX 11.00 & 11.11 (11i v1) PA-RISC)
- HPjconfig Configuration Tool
- Compiler Safe Points (HP-UX 11.00 & 11.11 (11i v1) PA-RISC)
- Using Linker Option +noenvvar and +compat on HP Integrity and PA-64 Systems
- Running Java with setuid or setgid
- HP Integrity (Itanium) Known Issues
- Using pthread_suspend() under certain conditions on HP-UX 11.31 (11i v3)
- Initializing a JVM instance with JNI_CreateJavaVM or attaching to JVM with AttachCurrentThread()
- Using Linker Option +noenvvar and +compat on HP Integrity and PA-64 Systems
- Running Java with setuid or setgid
- Running Aries HP Integrity emulation on PA2.0
- Software Support
- Security fixes in the 1.4.2.28 release

Dynamic TLS is not available on any HP-UX PA-RISC system. However there is a
workaround. See shl_load HotSpot libjvm problem due to TLS (HP-UX 11.0
PA-RISC) (page 22) in these release notes for details.
Signal Chaining Functionality
With signal chaining functionality, applications can now use signals that the JVM uses
and they will not interfere with the JVM's functionality. For signal chaining, the
application must load the library libjsig.sl (PA) or libjsig.so (Itanium) before
libc.2.
On PA-RISC, to obtain this functionality, you need to install the patch shown below
and then use LD_PRELOAD. On HP Integrity, no patch and no workaround is needed.
HP-UX 11.11 PA-RISC systems, install patch PHSS_28436 (or the patch that supersedes
it)
For examples and scenarios of how to use LD_PRELOAD, refer to the “Signal chaining
functionality” section of the HP-UX Programmer's Guide for Java 2.
Support for C++ applications built with -AA and -AP options (PA-RISC) only
Java supports the -AA and -AP options to build C++ applications. On HP Itanium
systems, the C++ runtime libraries support -AA and -AP by default. On HP-UX 11.11
and later releases on PA-RISC systems, C++ uses the -AP runtime option by default. If
you are using the ANSI Standard C++ runtime (-AA) option in an application that loads
Java, you need to use the -AA version of libjvm and libfontmanager.
Note that these libraries are provided as a separate download on the same page from
where you download the SDK and RTE, starting at this webpage: SDK and RTE 1.4.2.x
Downloads and Documentation.
These are the Standard C++ Runtime version of these libraries:
./jre/lib/PA_RISC2.0/libjvm_v2.sl
./jre/lib/PA_RISC2.0W/libjvm_v2.sl
./jre/lib/PA_RISC2.0/libfontmanager_v2.sl
./jre/lib/PA_RISC2.0W/libfontmanager_v2.sl
Any native application must be either linked with, or must dynamically load these
versions of the Java libraries if the C++ application is compiled using -AA.
The Standard C++ version of the JVM libraries are supported for PA_RISC2.0 and
PA_RISC2.0W architectures only.
If the JVM is invoked through the standard Java driver, then use the -V2 option to use
the Standard C++ runtime. For example:
java -V2 <javaprog>
Using Java 2 JNI on HP-UX
For C and C++ applications, it is important to link with the -mt (multithread) option
if the application calls a Java VM. Both executables and shared libraries must be linked
16