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

7 Using Signals
HP-UX Signal Interfaces
HP-UX defines several signal interfaces that allow a process to specify the action taken
upon receipt of a signal. The man pages sigaction(2), signal(2), sigvector(2),
bsdproc(2), and sigset(2V) describe the various HP-UX signal interfaces. The
man page signal(5) describes the HP-UX signals.
There are two HP-UX signal types, asynchronous and synchronous. Asynchronous
signals are not usually attributable to execution of code; synchronous signals are usually
attributable to execution of code.
Asynchronous signals include the keyboard-generated signals such as SIGINT and
SIGQUIT, and the sent-to-process signals such as SIGHUP. Synchronous signals include
hardware generated signals such as SIGSEGV, SIGBUS, and SIGFPE and the
sent-to-process signals such as SIGPIPE and SIGSYS.
HP-UX signals and the JVM
HP-UX signals and the JVM
The information below describes the HP-UX signals handled by the Java™ virtual
machine (JVM) and describes the effect once the JVM receives the signal.
The HotSpot and Classic VMs on PA-RISC and Itanium uses the following signals:
SIGSEGV
SIGALRM
SIGPIPE
SIGBUS
SIGILL
SIGFPE
SIGUSR1
SIGQUIT
Signals used internally by the JVM should not be generated by native methods, their
handlers must not be overridden, and they should not be blocked for extended periods.
In particular, none of these signals should be blocked when making a call from a native
method back into the JVM.
In addition, the SIGABRT signal handler can be overridden, but the handler should,
for correct semantic program execution, cause the termination of the JVM. SIGBUS is
reserved for future internal use by the JVM and native methods should not attempt to
install handlers for it.
Signal handlers for all of the other signals listed here may be overridden by native
methods and used freely. Signals not listed here may be freely used by native methods.
SIGHUP, SIGINT, and SIGTERM are asynchronous signals that cause a silent termination
of the JVM.
40 Using Signals