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
Replaced by the -Xusealtsigs option. Instructs the JVM to use SIGUSR2 instead of
the default SIGUSR1 to control the behavior of the JVM runtime. When your application
requires use of a native code library that uses SIGUSR1, use this option to avoid a
conflict between the two runtimes.
The HotSpot VM for Itanium systems uses the following immediate value ranges on
break instructions for internal use. Native program code must not execute a break
instruction with the immediate operand in any of these ranges,or HotSpot will intercept
and interpret the SIGimm signal received by the operating system when the break
instruction is encountered.
0x48000 - 0x49000
0x4c000 - 0x80000
Signal chaining functionality
Beginning with JDK 1.4 a new feature was added for chaining an application's signal
handlers behind the JVM's signal handlers. With signal chaining functionality,
applications can now use signals that the JVM uses and not interfere with the JVM's
functionality. To obtain this functionality, you need to install a HP-UX patch (described
below).
For signal chaining functionality, the application must load the library libjsig.sl
before libc.2.
libjsig.sl takes care of signal chaining when the application's signal handlers are
installed before or after the VM's handlers get installed. libjsig.sl is not needed when
the application installs the handlers before the JVM installs its handlers.
There are two cases to consider:
1. Native application creates a JVM
The application can either link in libjsig.sl and ensure that libjsig.sl
gets loaded before libc.2 by linking them in the right order or use the
LD_PRELOAD_ONCE functionality provided by the linker to load libjsig.sl
first.
2. Normal Java application invoked from the command line
LD_PRELOAD_ONCE must be used in this case. Linking the native libraries with
libjsig will not work because the JVM will load libc.2 before the application's
shared libraries get loaded.
For example, to use the LD_PRELOAD_ONCE environment variable as follows:
LD_PRELOAD_ONCE=/some/lib/I/care/about.sl; program ...
To obtain the LD_PRELOAD_ONCE functionality, you need to install the patch (or
the patch that supersedes it) shown below.
For HP-UX 11.00 systems, install patch PHSS_26559. For HP-UX 11.11 systems,
install patch PHSS_26560.
42 Using Signals