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

• Security tools (keytool, jarsigner, policytool, kinit, klist, ktab)
• Java™ IDL and RMI-IIOP Tools (tnameserv, idlj, orbd (1.4 only), servertool)
Setting the class path
The class path is the path that the Java™ runtime environment searches for classes and
other resource files.
For information on how to set the class search path (more commonly known by the
shorter name, "class path") refer to Oracle's documentation at: http://
download.oracle.com/javase/1.4.2/docs/tooldocs/solaris/classpath.html
How classes are found
For documentation on how the Java™ launcher and javac and javadoc find classes,
refer to Oracle's documentation at: http://download.oracle.com/javase/1.4.2/docs/
tooldocs/findingclasses.html
Excluding methods from being compiled
To prevent the HotSpot runtime compiler from compiling certain methods, you can
create a file called .hotspot_compiler and add the method to be excluded to the
file.
For example, if you want to exclude java/lang/String.indexOf() from being
compiled, you would add the following line to the .hotspot_compiler file:
exclude java/lang/String indexOf
By default, the HotSpot VM looks for .hotspot_compiler under the directory where
libjvm.sl resides. In addition, it looks for a .hotspot_compiler file in the current
directory where the JVM was started.
For example, if you are running the JVM on a PA2.0 server, narrow mode, and the JVM
was started from a script called run.sh in the directory /app/myapp/bin, it first
looks in the directory {JAVA_HOME}/jre/lib/PA_RISC2.0/server and then it
looks for a .hotspot_compiler file in the /app/myapp/bin directory.
Another way to exclude a method is to specify the .hotspot_compiler file using
the VM option-XX:CompileCommandFile=<list of .hotspot_compiler
files separated by ":">
For example:
-XX:CompileCommandFile=/tmp/foo/.hotspot_compiler_app_version_71:\
/tmp/foo2/hc81
If you specify the -XX:CompileCommandFile option it overrides the default behavior
of the VM and the VM will NOT scan either the libjvm.sl directory or the current
directory for a .hotspot_compiler file.
10 HotSpot Technology Tools and Commands