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
-Dhpux.im.enable.awt (version 1.2.2 and later)
This option is a workaround to allow the java input method to work with European
locale composed characters. Using this option will disable the java input method for
the Asian locale.
-Dhp.swing.use FastSwing (version 1.3.1 only)
This option improves the performance of swing APIs for Java™ for HP-UX version
1.3.1.
-pa11 (version 1.2.2 and later on PA-RISC only)
NOTE: If you run HotSpot with the -pa11 flag or run on a PA 1.1 system, your heap
address space will be restricted to 1G.
PA1.1 binaries can be run on PA1.1 as well as PA2.0 systems; however, The PA2.0
shared libraries are the default if you are running on a PA2.0 system. You can override
the use of the PA2.0 shared libraries on a PA2.0 system by specifying the -pa11 flag.
On a PA2.0 based system, if you invoke Java™ as follows, the default PA2.0 shared
libraries are used:
java -version
If you invoke Java™ with the -pa11 option as follows, the PA1.1 shared libraries are
used:
java -pa11 -version
-verbosegc
Prints out the result of a garbage collection to the stdout stream. At every garbage
collection, the following 5 fields are printed:
[%T %B->%A(%C), %D]
%T is "GC:" when the garbage collection is a scavenge, and "Full GC:" when its a full
garbage collection. A scavenge collects live objects from the New Generation only,
whereas a full garbage collection collects objects from all spaces in the Java™ heap.
%B is the size of Java™ heap used before garbage collection, in KB.
%A is the size after garbage collection, in KB.
%C is the current capacity of the entire Java™ heap, in KB.
%D is the duration of the collection in seconds.
-Xbatch
(Excerpt below from Oracle's documentation.)
Disable background compilation. Normally, if compilation of a method is taking a long
time, the VM will compile the method as a background task, running the method in
interpreter mode until the background compilation is finished. The -Xbatch flag
disables background compilation so that compilation of all methods proceeds as a
Standard and non-standard options 15