HP-UX Java™ SDK, RTE, and Plug-In 1.4.2.18 Release Notes

• Sun Micro systems' 1.4.2_14, 1.4.2_15, 1.4.2_16, and 1.4.2_17 release*

• Performance enhancements and defects fixed in previous 1.4. releases as well as the defects shown in "Problem Fixes."

• Support for C++ -AA and -AP options PA-RISC

• HotSpot 1.4.2.18 server JVM

• Java Web Start

• Runs in 32-bit or 64-bit mode on both PA-RISC and HP Integrity-based systems

* Please note that on occasion HP backports a defect fix from a Sun release that has not yet been merged into our current sources. Therefore a Sun defect may be fixed in an HP release even though the Sun release that contains the fix is not part of the HP release.

HotSpot 1.4.2.18 Server JVM

All -X options that were in earlier HotSpot JVMs are included in HotSpot 1.4.2.18. Performance, tool support, tool enhancements, and features are documented at http://java.sun.com/j2se/1.4.2/docs/.

The HotSpot 1.4.2.18 Server JVM for HP-UX 11 PA-RISC and HP Integrity systems is suitable for both client and server workloads. We invoke the Server VM with configuration options that suit client-side applications.

The SDK 1.4.2.18 HotSpot 1.4.2.18 Edition supports the APIs core to the Java 2 platform: Java Foundation Classes (JFC), Security, Java IDL, JDBC™, JavaBeans™, Remote Method Invocation (RMI), Java 2D, the Collections Framework, and a new set of nonblocking i/o APIs.

The Java 2 Platform version 1.4.2 API Specification is available at http://java.sun.com/j2se/1.4.2/docs/api/

Here is a partial list of the functionality that the HotSpot 1.4.2.18 Server JVM provides:

• Improved performance

• Nonblocking I/O APIs
  Introduced in 1.4.1, they are now part of the Java system libraries under the package java.nio. The previous implementation of I/O multiplexing using the class com.hp.io.Poll is still being included for backward compatibility. We encourage you to upgrade and use the features provided through the new java.nio package.

• IPv6 support on HP Integrity and PA-RISC
  Please see "IPv6 support (Internet Protocol version 6) (SDK 1.4 and later)" in the HP-UX Programmer's Guide for Java 2 at HotSpot Technology Tools and Commands#IPv6 for usage information.

• Java VM Debugging Interface (JVMDI)
  JVMDI and JPDA allow you to run HotSpot with numerous development tools. For more information, refer to http://java.sun.com/j2se/1.4/docs/guide/jpda/architecture.html

• Java Platform Debugger Architecture (JPDA)
  Architecture and components are documented at http://java.sun.com/products/jpda/ and http://java.sun.com/j2se/1.4.2/docs/guide/jpda/. The jdb for HP-UX is similar to the Solaris implementation. For usage information, refer to Sun VM Invocation Options at http://java.sun.com/products/jpda/doc/conninv.html

• Java VM Profiling Interface (JVMPI)
  Support for JVMPI allows you to profile java code with the HotSpot 1.4 VM so you can extract more accurate runtime profiles.

• HP debugger WDB support
  Use HP's debugger WDB 3.0.01 or later to examine backtraces containing mixed language frames (Java and C/C++) in Java thread stacks. This simplifies debugging the VM and Java mixed-language applications. For more information, refer to "Using WDB to examine backtraces in Java thread stacks" in the HP-UX Programmer's Guide for Java 2 at: Debugging#wdb_debug.

• -Xeprof option: Generates profile data for HPjmeter.
  For syntax and use, refer to the HP-UX Programmer's Guide for Java 2 at HotSpot Technology Tools and Commands#-Xeprof

• Large heap sizes
  Heaps up to 3.5GB are supported on HP-UX 11.23 (11i v2) (no patches required), and up to 3GB on HP-UX 11.11 PA (11i v1) with the installation of patches. Refer to the sections on expanding memory in the HP-UX Programmer's Guide for Java 2 at: Expanding Memory

• 64-bit mode
  Supported by using the option -d64. For further information, refer to the HP-UX Programmer's Guide for Java 2 at HotSpot Technology Tools and Commands#-d64

• Support for Java 3D
  For information on HP's Java 3D technology, see "3D for SDK & RTE overview & features" at Java™ 3D for SDK and RTE Downloads and Documentation

• New garbage collectors
  Supports parallel and concurrent mark and sweep garbage collectors. For a detailed look at garbage collection and the new collectors, refer to JavaSoft's documentation "Tuning Garbage Collection with the 1.4.2 Java Virtual Machine" at http://java.sun.com/docs/hotspot/gc1.4.2/index.html.

• Java Web Start bundled with the RTE
  The files for Java Web Start technology are part of the jre in the directory javaws. Web Start release notes are also included in the javaws directory.

• HeapDump Options:
  • -XX:+HeapDump
    The HeapDump command line option can be used to observe memory allocation in a running Java application by taking snapshots of the heap over time. Using the _JAVA_HEAPDUMP=1 environment variable allows memory snapshots to be taken without modifying the java command line. The HeapDump functionality is available starting with SDK 1.4.2.10 and JDK 5.0.03. For further information, refer to the HP-UX Programmer's Guide for Java 2 at HotSpot Technology Tools and Commands#-XX:+HeapDump. Please also note the section on 'Interaction of HeapDump Options'.

  • -XX:+HeapDumpOnly
    The HeapDumpOnly option can be used to enable HP Heap Dumps using SIGVTALARM signal (signal 20). Using the environment variable, _JAVA_HEAPDUMP_ONLY, the HeapDump functionality is triggered without modifying the java command line. For further information, refer to the HP-UX Programmer's Guide for Java 2 at HotSpot Technology Tools and Commands#HeapDumpOnly. Please also note the section on 'Interaction of HeapDump Options'.

  • XX:+HeapDumpOnOutOfMemory
    The HeapDumpOnOutOfMemory command line option causes the JVM to dump a snapshot of the Java heap when an Out Of Memory error condition has been reached. The HeapDumpOnOutOfMemory functionality is also available in JDK 1.5.0.04. For further information, refer to the HP-UX Programmer's Guide for Java 2 at HotSpot Technology Tools and Commands#HeapDumpOnOutOfMemory.

  • -XX:+HeapDumpOnCtrlBreak
    The option -XX:+HeapDumpOnCtrlBreak enables the ability to take snapshots of the Java heap when a SIGQUIT is sent to the Java process, without using the jvmti-based -Xrunhprof:heap=dump. This feature is similar to the -XX:+HeapDump option, except the output format is binary hprof format, and is placed into a filename. The HeapDumpOnCtrlBreak functionality is also available with JDK 5.0.05. For further information, refer to the HP-UX Programmer's Guide for Java 2 at HotSpot Technology Tools and Commands#HeapDumpOnCtrlBreak. Please also note the section on 'Interaction of HeapDump Options'.

*** IMPORTANT NOTE for PA-RISC Customers! ***

HP-UX 11.11 (11i v1) PA-RISC Required patch PHNE_29887 solves socket problems that may cause hangs

For all SDK versions 1.4.2.xx, the pthreads patch shown below (or its superseded patch) must be installed for HP-UX 11.0 or HP-UX 11.11 (11i v1)PA-RISC. The patch is not required for HP Integrity.

HP-UX 11.0 PA-RISC Required patch PHCO_29959 or
HP-UX 11.11 (11i v1) PA-RISC Required patch PHCO_29960

To determine which patches have been installed on your machine, log in as root and check your machine with:

/usr/sbin/swlist -l product

For a complete list of required and recommended patches (which includes the patches mentioned above), refer to the web page shown below. Please install ALL dependency patches as well. These will be listed on the IT Resource Center web page from where you download the patch: Patch Information

Operating system patches should be installed before you install the SDK.

HP-UX PA-RISC System requirements

The Java technology requires HP-UX HP PA-RISC systems 11.11 (11i v1), 11.23 (11i v2), and 11.31 (11i v3). (HP-UX 11.20 and 11.22 are not supported.) The minimum system for running Java applications is a PA-RISC 2.0 system.

HP-UX HP Integrity System Requirements

The Java technology requires HP-UX 11.23 (11i v2) and 11.31 (11i v3). (HP-UX 11.20 is not supported.) Refer to the following web site for HP Integrity servers: HP Integrity Servers

Installation instructions

You need a total of approximately 160 MB of disk space to download and install the .depot file. The download file runs on both Workstations and Servers. After installing the software, you can remove the .depot file.

Note:   When downloading a .depot file, some browsers don't recognize the .depot format and treat the file as a text file.  If this happens, right-click the Download Directly >> button (on the Software download confirmation window) and select Save Target As....

To verify that the file downloaded correctly you need to use MD5 Secure Checksum (md5sum).   You can download MD5 Secure Checksum at HP-UX MD5 Secure Checksum if you do not already have this utility.   To verify your download with MD5 Secure Checksum, at the UNIX prompt, execute the command:
md5sum <filename>
If the file downloaded correctly, the checksum number for the file you downloaded should match the MD5 Checksum number given for that file.

The SDK for the Java™ Platform installs under /opt/java1.4. The RTE is installed under /opt/java1.4/jre. If you have a previous installation of 1.4, please uninstall it using swremove and move any personal files from your existing /opt/java1.4 directory before you begin the new installation. If you do not uninstall a previous installation, you may see messages such as "Error: You have specified more than one fileset selection." As root user, use the following SD-UX swinstall command to install the software:

/usr/sbin/swinstall

This command will lead you through the installation. Change Source Depot Type to "Local Directory" and Source Depot Path to /tmp/<filename>. (If you used a directory other than /tmp in the previous step, replace /tmp with that directory name.) We recommend you select the "Reinstall filesets" and unselect the "Mount file systems" option from the options menu.

WARNING: Do not unarchive rt.jar, charsets.jar, jpda.jar, tools.jar, jce.jar, and jsse.jar. These files are needed by the SDK tools and the runtime environment.

Add the directory /opt/java1.4/bin to your PATH.

Note: To install the software into an alternate location, see the next sections "Installing into an Alternate Location."

For information on setting important system parameters required for correct execution of Java programs refer to the Programmer's Guide which can be found at Programmer's Guide for Java™ 2.

Setting install options using Software Depot Install (SD Install)

1. To set install options, click the Options menu on the main SD Install window and click Change Options. We recommend setting the following install options:
   • Deselect Mount file systems in /etc/fstab or /etc/checklist.
   • Select Reinstall filesets even if same revision exists.
2. From the Actions menu click Change Source...
3. Select Local Directory as the Source Depot Type.
4. Enter the Source Host Name.
5. Enter the Source Depot Path. If for example you downloaded the .depot file to the /tmp directory you would enter: /tmp/sdk14_14208_1122.depot
6. If you used a directory other than /tmp in step two, replace /tmp with that directory name.
7. Click OK and SD Install will guide you through the installation.

If you are having problems with the software installation, refer to Software Support in these release notes.

Verifying file download

To verify that the file downloaded correctly, at the UNIX prompt run the command cksum <filename>. If the file downloaded correctly, the checksum number for the file you downloaded should match the checksum number given above for that file.

Installing into an alternate location

To install the software into an alternate location, add @/<alternatedirectory> to the end of the swinstall line, and add the alternate directory to your PATH.

For example:

/usr/sbin/swinstall -s <download> \* @/<alternatedirectory>

Java prepends <alternatedirectory> to the default product path. Java will therefore install in /alternatedirectory/opt/java1.4.

If you want your Java home directory in <alternatedirectory> without the /opt/java1.4 directories, you need to install into a temporary directory, and then move the directories to where you want them.

For example:

swinstall -s <download> \* @/<temporarydirectory>
mv <temporarydirectory>/opt/java*/* <finalalternatedirectory >

Or you can install and link to the directories.

For example:

swinstall -s <download> \* @/<actualdirectory>
ln -s <finalalternatedirectory> /<actualdirectory>/opt/java*

You will notice that the two files, <alternatedirectory>/etc and <alternatedirectory>/var are created. These may be purged, because they do not apply to a product installed in an alternate location.

Please note that Java does not use the SD configure step; "installed" is the same as "configured".

File structure SDK

The following diagram below displays an abbreviated form of the file structure:

  java1.4

     |

  ___|______________________________________________

   |        |        |            |           |        

  bin      lib      jre          demo     include 

   |        |       javaws files*

  java    tools.jar  | 

  javac   dt.jar     |

  javadoc ir.idl     |

  javah   orb.idl    |

  javap              | 

  jdb                |

                  ___|_____________________________

                     |                             |

                    bin                           lib

                     |                             |

________________________________________________   | 

java PA_RISC PA_RISC2.0 PA_RISC2.0W  IA64N  IA64W    |  

                                                   |

                                                   |

             __________________________________________________________________

             |      |    |       |        |           |           |        | 

           rt.jar  zi security PA_RISC  PA_RISC2.0  PA_RISC2.0W  IA64N   IA64W 

        charsets.jar             |________|___________|___________|________|___  

          jce.jar                |        |           |           |        |        

          jsse.jar            server    server      server      server   server

		  

* The files for Java Web Start technology are part of the jre in the directory javaws. Web Start release notes are also included in the javaws directory.

The tools are under opt/java1.4/bin and the libraries install under opt/java1.4/lib. The tools.jar file contains the classes for supporting the tools and utilities. The file dt.jar contains the DesignTime archive of BeanInfo files.

The jre directory includes the runtime environment. The file rt.jar contains the runtime classes for the core API. The file charsets.jar contains the internationalization and localization classes and files. The security directory contains security management files.

The shared libraries used by the HP-UX platform are contained in the following directories:

The include directory contains the header files for supporting JNI and JVMDI.

File structure Runtime Plug-in (JPI) for Mozilla

The Runtime Plug-in for Mozilla for HP-UX requires the shared library(ies) loaded by the Mozilla browser, the remaining Runtime Plug-in files, and the RTE to be located in the following fixed relative position:

If the JPI is installed in the default location, /opt/java1.4/jre, the following links are created during install to allow the browser to locate the Runtime Plug-in shared library:

PA-RISC installation:

/opt/mozilla/plugins/libjavaplugin_oji.sl -> \ 

    /opt/java1.4/jre/plugin/PA_RISC2.0/mozilla/libjavaplugin_oji.sl 

HP Integrity installation:

/opt/mozilla/plugins/libjavaplugin_oji.sl -> \ 

    /opt/java1.4/jre/plugin/IA64N/mozilla/libjavaplugin_oji.sl

If the Runtime Plugin is installed in a non-default location, you or the system administrator needs to create similar links in order to enable Mozilla to find the Runtime Plug-in. Or you may use the environment variable MOZ_PLUGIN_PATH for Mozilla, which is described in the section below regarding configuration.

Information on Mozilla for HP-UX is at Mozilla Web Browser for HP-UX Downloads and Documentation. Additional Plug-in documentation and FAQs can be found at http://java.sun.com/products/plugin.
 

The Java for HP-UX Programmer's Guide at Programmer's Guide for Java™ 2 contains usage documentation for developers. There you will find information on HotSpot options, HP-specific options and features, suggestions and examples for allocating memory, how to use WDB to examine backtraces in Java threads, code examples for using Java Native Interface, and much more.

Another change is that beginning with 1.4.2.08, we are combining the SDK, RTE, and Runtime Plug-in release notes in this document.

For additional documentation web sites, refer to "Additional HP and Sun documentation" in these release notes.

SDK Usage

Removing support for unwanted architectures in the RTE

Under the RTE license agreement, partners who redistribute the RTE may remove support for unwanted architectures. Functional components may NOT be removed under any circumstances. Beginning with this 1.4.2.05 release, you may remove support for unwanted architectures as follows:

The following commands assume that the RTE has been installed in the standard location, i.e. /opt/java1.4/.

The swremove commands must be run as root. Use these command lines:

• On a PA-RISC or HP Integrity (Itanium) system, to remove PA_RISC 1.1 support:

/usr/sbin/swremove Jre14.JRE14-PA11 Jre14.JRE14-PA11-HS
(The -pa11 command line option will no longer work.)

• On a PA-RISC system, to remove 64-bit support:

/usr/sbin/swremove Jre14.JRE14-PA20W Jre14.JRE14-PA20W-HS
(The -d64 command line option will no longer work.)

• On an HP Integrity (Itanium) system, to remove 64-bit support:

/usr/sbin/swremove Jre14.JRE14-IPF64 Jre14.JRE14-IPF64-HS
(The -d64 command line option will no longer work.)

• PA_RISC 2.0 support is not typically installed on HP Integrity, but if it is, to remove it:

  
  /usr/sbin/swremove Jre14.JRE14-PA20 Jre14.JRE14-PA20-HS \
  
           Jre14.JRE14-PA20W Jre14.JRE14-PA20W-HS
  
  

Support for dynamic thread local storage (TLS)

Dynamic thread local storage is fully supported on all HP Integrity (Itanium) systems, beginning with SDK Versions 1.4.2.00 and 5.0.

Dynamic TLS is not available on any HP-UX PA-RISC system. However there is a workaround. Refer to "shl_load HotSpot libjvm problem due to TLS (PA-RISC)" in these release notes for details.

Signal Chaining Functionality

With signal chaining functionality, applications can now use signals that the JVM uses and they will not interfere with the JVM's functionality. For signal chaining, the application must load the library libjsig.sl (PA) or libjsig.so (Itanium) before libc.2.

On PA-RISC, to obtain this functionality, you need to install the patch shown below and then use LD_PRELOAD. On HP Integrity, no patch and no workaround is needed.

HP-UX 11.11 PA-RISC systems, install patch PHSS_28436 (or the patch that supersedes it)

For examples and scenarios of how to use LD_PRELOAD, refer to the Java for HP-UX Programmer's Guide at: Using Signals#chaining

Support for C++ applications built with -AA and -AP options (PA-RISC)

Java supports the -AA and -AP options to build your C++ product. On HP Itanium systems, the C++ runtime libraries support -AA and -AP by default. On HP-UX 11.0 or 11.11 PA-RISC, if you are using the ANSI Standard C++ runtime (-AA) option in an application that loads Java, you need to use the -AA version of libjvm and libfontmanager. Note that these libraries are provided as a separate download on the same page from where you download the SDK and RTE, starting at this webpage:
SDK and RTE 1.4.2.x Downloads and Documentation

These are the Standard C++ Runtime version of these libraries:

./jre/lib/PA_RISC2.0/libjvm_v2.sl
./jre/lib/PA_RISC2.0W/libjvm_v2.sl
./jre/lib/PA_RISC2.0/libfontmanager_v2.sl
./jre/lib/PA_RISC2.0W/libfontmanager_v2.sl

The native application must be linked with, or must dynamically load these versions of the Java libraries if your C++ application is compiled using -AA.

The Standard C++ version of the JVM libraries are supported for PA_RISC2.0 and PA_RISC2.0W architectures only.

If the JVM is invoked through the standard Java driver, then use the -V2 option to use the Standard C++ runtime.
For example:

java -V2 <javaprog>

Using Java 2 JNI on HP-UX

For C and C++ applications, it is important to link with the -mt (multithread) option if the application calls a Java VM. Both executables and shared libraries must be linked with -mt. Use of -mt must be consistent during both compilation and linking. For more information, refer to the Native (non-Java) calling Java methods section in the Programmer's Guide.

If you embed libjvm in a 32-bit native application and wish to use a large Java heap, you must link with the -N option. Refer to the Expanding heap size in native applications on PA-RISC HP-UX 11.11 and later releases and Expanding heap size in native applications on Integrity HP-UX 11.23 and later releases for more information.

HotSpot JVM Options

For all standard and non-standard options, please refer to the Java for HP-UX Programmer's Guide at HotSpot Technology Tools and Commands.

Garbage collectors: Parallel, Concurrent mark, and Sweep

JavaSoft has implemented new generational collectors that emphasize the throughput of the application or low garbage collection pause times.

For a detailed look at garbage collection and the new collectors, refer to JavaSoft's documentation "Tuning Garbage Collection with the 1.4.2 Java Virtual Machine" at http://java.sun.com/docs/hotspot/gc1.4.2/index.html

Allocating physical memory and swap in the Java heap

The method of allocating physical memory and swap within the Java heap has changed. As a result, you are likely to see higher RSS (resident set size) memory usage when monitoring your Java processes with Glance or other tools, or your application startup may be slightly slower.

For more details on why this occurs and for examples of using key command line options, see: Allocating Physical Memory and Swap in the Java Heap.

Asian TrueType fonts and Asian locales

Asian Locales are supported by HP's 1.4 JDK with TrueType fonts. For more details, please refer to HP-UX Fonts and the Java™ Runtime Environment.

Date/Time methods - New defaults

The HotSpot JVM uses the gettimeofday() system call to obtain date and time information.

For performance reasons a new mechanism is used that uses the number of CPU ticks since the application started, to calculate the current time. As a result, changes to the system date or time using date(1), adjtime(2) or time synchronization utilities such as ntp will not be reflected in the date and time that the Java program returns, until the process is restarted.

If your application requires that system time changes are immediately reflected, you can use the
-XX:+UseGetTimeOfDay option to tell the JVM to use the gettimeofday call instead of the new, lightweight mechanism. However you may notice a drop in performance.

Profiling

In the SDK Version 1.4, a SIGPROF handler to support future profiling capability is installed automatically. This may cause incompatibilities with other native code or profiling tools which use SIGPROF.

You can turn off the SIGPROF handler by using the following option -XX:+ReduceSignalUsage

However be aware that using this option also turns off the SIGQUIT handler, and you therefore will not be able to get a Java stack trace.

Closing a socket when accept or read is pending (PA-RISC) - new patch information!

Because of changes to the mechanism by which a socket is closed in the VM, for all supported HP-UX PA-RISC systems, you no longer need to use the -XdoCloseWithReadPending option we recommended in earlier releases. However for HP-UX 11.11 the following patches (or their superseded patches) are required:

PHKL_32457
PHKL_25840
PHKL_25842
PHNE_25644
PHNE_25084

For more detailed information, refer to the Java for HP-UX Programmer's Guide at HotSpot Technology Tools and Commands#socket

Compatibility with previous releases

Sun Microsystems maintains upward 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 API's are introduced that cannot be run on earlier JVMs.

For a detailed description of the incompatibilities between 1.3 and 1.4, refer to http://java.sun.com/j2se/1.4/compatibility.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, refer to the Plug-In FAQs at Java™ Runtime Plug-in (JPI) for 1.3, 1.4, 5.0, & 6.0 Frequently Asked Questions.

Additional HP and Sun documentation

The following web sites have additional information:

Known JavaSoft bugs are documented in the Bug Database at http://developer.java.sun.com/

Problem fixes

Please note that on occasion HP backports a defect fix from a Sun release that has not yet been merged into our current sources. Therefore a Sun defect may be fixed in an HP release even though the Sun release that contains the fix is not part of the HP release.

This 1.4.2.18 release includes the enhancements and defects fixed in previous HP 1.4.2 releases and in Sun's 1.4.2_14, 1.4.2_15, 1.4.2_16, and 1.4.2_17 as well as the following additional defect fixes and Sun Alerts:

Infrequently, a finalizer is not run and the expected clean-up of any objects and resources performed in that finalizer does not occur. Symptoms can include exhaustion of available system resources including file descriptors and memory.

A fix for this problem is included in HP's SDK version 1.4.2.13 and later and JDK version 5.0.07 and later.

PA-RISC Known Issues

Below is some information on known PA-RISC defects. Some of the solutions require installing patches. For more information on locating and installing patches, go to: Patch Information

HP Integrity (Itanium) Known Issues