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
Compatibility with previous releases
Oracle maintains upwards compatibility. Therefore, an application written for a 1.3
JVM will run on a 1.4 JVM. Downward compatibility is generally not supported because
new APIs are introduced that do not run on earlier JVMs.
For a detailed description of the incompatibilities between 1.3 and 1.4, refer to http://
java.sun.com/javase/compatibility_j2se1.4.html .
Runtime Plug-In usage and configuration
You can configure the Runtime Plug-In by running the Control Panel script, which
launches the Control Panel java application, or by loading ControlPanel.html in the
browser. Both files are found in the directory jre/bin and jre/, respectively, under
the directory where the Runtime Plug-in has been installed.
The Control Panel application generates a file:
$HOME/.java/deployment/deployment.properties
This file contains, among other settings, the path to the RTE to be used by the Runtime
Plug-in for HP-UX when the browser loads an applet from a Runtime Plug-in enabled
html page. If the Plug-in is installed in the default location, this setting is stored in the
key:
javaplugin.jre.path=/opt/java1.4/jre
No environment variables are necessary for configuring the Runtime Plug-In for HP-UX,
Java Edition. However, you may optionally use the following environment variables.
MOZ_PLUGIN_PATH
You can use the MOZ_PLUGIN_PATH environment variable to direct the Mozilla browser
to search alternate directories for plug-in libraries.
NOTE: The entries in the $HOME/.java/deployment/deployment.properties
file supersede those of MOZ_PLUGIN_PATH when locating the RTE.
CLASSPATH
A user's CLASSPATH environment variable can be passed by the JVM by running the
Control Panel and specifying either -cp or -classpath in the "Java Run Time
Parameter" box. You need to exit and rerun the browser for this change to take effect.
For additional information on the Runtime Plug-In, see the Java™ Runtime Plug-in (JPI)
Frequently Asked Questions at:
http://www.hp.com/go/hpux-java-docs
Enabling HTML pages to use the Runtime Plug-in for HP-UX
The first time the Mozilla browser loads an applet from a Runtime Plug-in-enabled
HTML page, it will download and install the Runtime Plug-in for HP-UX. Oracle has
provided some additional tools to assist users in using Plug-in products. They have
provided a converter to automate the enabling on HTML pages. They also provide an
HTML specification for users who wish to enable their HTML pages manually.
92 SDK/RTE 1.4.2.n Usage Notes