HP-UX Programmer's Guide for Java 2
Table Of Contents
- Table of Contents
- 1 Introduction
- 2 HotSpot Technology Tools and Commands
- 3 Configuration for Java™ Support
- 4 Performance and Tuning
- 5 Measuring System Performance
- 6 Using Threads
- 7 Using Signals
- 8 Using Java™ 2 JNI on HP-UX
- 9 Expanding Memory
- Determine your requirements
- Memory layout under HP-UX 11.0 (PA-RISC only)
- Additional memory available under HP-UX 11i (PA-RISC only)
- Allocating physical memory and swap in the Java™ heap
- Useful key command-line options for allocating memory
- Application-dependent considerations using large heap size HP-UX 11i PA-RISC
- Expanding heap size in native applications on PA-RISC HP-UX 11.11 and later releases
- Expanding heap size in native applications on Integrity HP-UX 11.23 and later releases
- Expanding heap size in HP-UX PA-RISC
- Expanding heap size in HP-UX Integrity
- 10 Diagnosing Memory Leaks
- A JDK/JRE 6.0.n and 7.0.n Usage Notes
- Using Java 2 JNI on HP-UX
- Garbage collection
- Asian TrueType fonts and Asian locales
- Date/Time methods defaults
- Profiling
- Compatibility with previous releases
- Java Cryptography Extension (JCE) policy files
- Configuring the Java Runtime Plug-In
- CLASSPATH environment variable
- Java Web Start technology usage
- Upgrading from a previous Java Web Start version
- IPv6 support
- Allocation Site Statistics and Zero Preparation -Xverbosegc
- JDK 6.0.04 flags
- GC log-rotation support
- NUMA collector enhancements
- ThreadDumpPath support
- Garbage-First garbage collector (-XX:+UseG1GC)
- jmap, jinfo, and jstack tools included in JDK 6.0.03
- Additional Java Web Start documentation
- B JDK/JRE 5.0.n Usage Notes
- Using Java 2 JNI on HP-UX
- Garbage collectors: Parallel and Concurrent Mark Sweep
- Allocating physical memory and swap in the Java heap
- Asian TrueType fonts and Asian locales
- Date/Time methods defaults
- Profiling
- Closing a socket (PA-RISC only)
- Compatibility with previous releases
- Java Cryptography Extension (JCE) policy files
- Allocation Site Statistics and Zero Preparation -Xverbosegc
- IPv6 support on Java 5.0
- GC log-rotation support in 5.0
- ThreadDumpPath support in 5.0
- Dynamically loaded libraries in 5.0
- Performance improvement for String.intern()
- Configuring the Java Runtime Plug-In
- CLASSPATH environment variable
- Java Web Start technology usage
- C SDK/RTE 1.4.2.n Usage Notes
- Removing support for unwanted architectures in the JRE
- Support for dynamic thread local storage (TLS)
- Signal Chaining functionality
- Using Java 2 JNI on HP-UX
- HotSpot JVM options
- Garbage collectors: Parallel and Concurrent mark 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
- D Additional Resources
- Index

patches). For HP-UX 11.11 (11i v1), the feature is included. For more information on
LD_PRELOAD functionality and limitations, read the man page for dld.sl after you
have installed the patch.
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, see “Signal chaining
functionality” (page 42).
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
with -mt. Use of -mt must be consistent during both compilation and linking. For
more information, see “Native (non-Java) calling Java™ methods” (page 52).
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, see “ Expanding heap size in
native applications on PA-RISC HP-UX 11.11 and later releases” (page 67) and
“Expanding heap size in native applications on Integrity HP-UX 11.23 and later releases”
(page 67).
HotSpot JVM options
For all standard and non-standard options, please refer to Chapter 2 (page 8).
Garbage collectors: Parallel and Concurrent mark 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.
90 SDK/RTE 1.4.2.n Usage Notes