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
with -mt. Use of -mt must be consistent during both compilation and linking. For
more information, refer to the “Native (non-Java) calling Java methods” section in the
HP-UX Programmer's Guide for Java 2 on the BSC at http://www.hp.com/go/
hpux-java-docs.
If you embed libjvm in a 32-bit native application and wish to use a large Java heap,
you must link with the -N option. For more information, refer to the “Expanding heap
size in native applications on PA-RISC HP-UX 11.11 and later releases” and “Expanding
heap size in native applications on Integrity HP-UX 11.23 and later releases,” also in
the HP-UX Programmer's Guide for Java 2.
HotSpot JVM Options
For all standard and non-standard options, please refer to the HotSpot Technology
Tools and Commands section of the HP-UX Programmer's Guide for Java 2.
Garbage collectors: Parallel, Concurrent mark, and Sweep
JavaSoft has implemented new generational collectors that emphasize the throughput
of the application or low garbage collection pause times.
For a detailed look at garbage collection and the new collectors, refer to JavaSoft's
documentation "Tuning Garbage Collection with the 1.4.2 Java Virtual Machine" at
http://java.sun.com/docs/hotspot/gc1.4.2/index.html and http://www.oracle.com/
technetwork/java/javase/tech/index-jsp-140228.html.
Allocating physical memory and swap in the Java heap
The method of allocating physical memory and swap within the Java heap has changed.
As a result, you are likely to see higher RSS (resident set size) memory usage when
monitoring your Java processes with Glance or other tools, or your application startup
may be slightly slower.
For more details on why this occurs and for examples of using key command line
options, see the “Allocating Physical Memory and Swap in the Java Heap” section of
the HP-UX Programmer's Guide for Java 2.
Asian TrueType fonts and Asian locales
Asian locales are supported by HP's JDK 1.4 with TrueType fonts. For more details,
see HP-UX Fonts and the Java™ Runtime Environment at:
http://www.hp.com/go/hpux-java-docs
Date/Time methods defaults
The HotSpot JVM uses the gettimeofday() system call to obtain date and time
information. For performance reasons a new mechanism that uses the number of CPU
ticks since the application started is used to calculate the current time. As a result,
changes to the system date or time using the date command, the adjtime() function,
Usage Documentation 17