HP-UX Java™ SDK Version 1.3.1.04 for Itanium Release Notes

»	SDK 1.3.1.04 (limited availability)
»	HP's version numbering
»	HotSpot version 1.3.1 server JVM
»	previous 1.3 releases

»	patches
»	minimum system recommendation
»	installation instructions
»	file structure

»	supported tools and options
»	additional HotSpot option information
»	hp specific options and features
»	support for locales
»	TrueType fonts

»	X windows, Java applications and TrueType fonts
»	the hp.fontpath property
»	bitmap vs. scalable fonts
»	the JAVA_FONTS environment variable
»	how the X font server affects font display
»	controlling the X font server

»	problem fixes and known issues

»	problem fixes
»	known issues
»	missing property files for Japanese printing
»	Asian TrueType fonts, swing, and xfs
»	using linker option +noenvvar on Itanimum and PA-64 systems
»	running Java with setuid or setgid

• Improved performance

• Full implementation of Java VM Debugging Interface (JVMDI)

• Support for Java VM Profiling Interface (JVMPI)

• Support for the -Xeprof option for HPjmeter

• Introduces a new option, -Xrs, which reduces the use of operating system signals by the Java Virtual Machine

• Large heap size (HP-UX 11i)

• Full implementation of JVMDI and JPDA allows you to run HotSpot instead of Classic when using the 1.3 SDK with numerous tools such as TogetherSoft Control Center, Code Warrior, Oracle JDeveloper, IBM Visual Age, Netbeans, JDE, MetaMata, Tek. Tools, Elixier IDE, BlueJ, JIG, JSwat Project, Swing Debugger, and the sample debugger jdb that ships with SDK 1.3.

• Support for JVMPI means that it is possible to profile java code with the HotSpot 1.3.1 VM. Therefore, you can extract more accurate runtime profiles. Some of the tools based on JVMPI include: hprof (-Xrunhprof), JProbe, JUM, and OptimizeIt. (Note: Although -hprof provides some stack trace information not found in -Xeprof, the latter can sometimes be more useful for performance tuning.) For more information on JVMDI and JPDA, go to http://java.sun.com/j2se/1.3/docs/guide/jpda/architecture.html

• The -Xrs option is fully documented at: http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/java.html

• The 1.3 release contains the FastSwing feature that is exclusive to HP-UX. This feature provides some performance improvement for Swing Applications on a Remote X-Server. Remote X-Servers include X-Terminals, PC-XServers like Exceed and Reflection X and remote unix workstations. This feature is documented in "Usage Documentation" below.

• JPDA is the debugging support architecture needed to build debugger applications for the Java 2 Platform. The JPDA includes the Java Debug Interface (JDI), the Java Debug Wire Protocol (JDWP), and the Java Virtual Machine Debug Interface (JVMDI). A sample debugger based on JPDA is provided in /opt/java1.3/bin/jdb. The original jdb product has been moved to /opt/java1.3/bin/oldjdb. Please note that the java source code for the sample debuggers is located in examples.jar in /opt/java1.3/demo/jpda and is unsupported.

• The 1.3release supports the APIs core to the Java 2 platform: Java Foundation Classes (JFC), Security, Java IDL, JDBC(tm), JavaBeans(tm), Remote Method Invocation (RMI), Java 2D, and the Collections Framework.

• HP also includes the implementation of a non-blocking I/O Poll API for Java in the com.hp.io package. com.hp.io.Poll supports a general mechanism for reporting I/O conditions associated with a set of FileDescriptors and for waiting until one or more conditions becomes true. Specified conditions include the ability to read or write data without blocking, and error conditions. Use of com.hp.io.Poll dramatically reduces the number of threads required to support large numbers of clients in large server-side Java applications.
  
  The packages included in the APIs core to the Java 2 platform are described at: http://java.sun.com/products/jdk/1.3/docs/api

• The JavaSoft idlj compiler is available in the 1.3 release. This allows developers to define their application interfaces in a program neutral interface language. The idl interface files are compiled into Java files via this compiler. It also generates portable client stubs and server skeletons that work with any CORBA-compliant Object Request Broker. It produces CORBA 2.3 compliant code. Refer to http://java.sun.com/reference/docs/index.html for more information.
  
  
  The Java Naming and Directory Interface (JNDI) is available in the 1.3 release. This makes it possible to have a federated naming service as part of your application. Currently LDAPv2, CosNaming, and RMI Registry Server Provider Interfaces are available on our JDK platform. Refer to http://java.sun.com/reference/docs/index.html for more information.

• The JavaSoft ORB has been updated to CORBA 2.3.2 compliancy. One of the new features specified in this update is "objects passed by value." Refer to the OMG documents at http://www.omg.org/ for more information on this CORBA version.

• New RMI run-time classes are included in this release. They provide greater performance and functionality for RMI applications running over the JRMP protocol.

• RMI/IIOP: New RMI run-time classes are included that allow RMI applications to run over the IIOP protocol.

• A new rmic compiler is provided that understands the "-iiop" option that produces stub and skeleton files that communicate via the IIOP protocol. This makes it possible for RMI clients and servers to communicate with their CORBA counterparts. Refer to http://java.sun.com/docs/index.html for more information.

The HP-UX SDK for the Java— 2 Platform installs under /opt/java1.3. As root user, use the SD-UX swinstall command to install the software:

/usr/sbin/swinstall

It 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 filesystems" option from the options menu in swinstall.

  java1.3
     |
  ___|_____________________________________________________
   |        |        |         |           |          |    
  bin      lib      jre      src.jar      demo     include 
   |        |        |
  java    tools.jar  |
  javac   dt.jar     |
  javap              |
  javah              |
  javadoc         ___|__________
  jdb                |          |
  ...               bin        lib
                     |          |
                    java  ______|___________________________________
                    ...       |          |         |             
                          rt.jar     security    IA64      
                         il8n.jar              ____|_____               
                                               |        |     
                                             classic  hotspot

Prints out a brief usage message describing the non-standard options.

Disables background compilation. If compilation of a large method is taking a long time, the performance engine will revert to interpreting the method. It 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 foreground task until completed, regardless of how long the compilation takes. This flag is provided for users who desire more deterministic behavior of method compilation for purposes such as benchmarking.

Specify a colon-separated list of directories, JAR archives, and ZIP archives to search for boot class files. The specified boot class libraries will be used instead of the boot class files in the jre/lib/rt.jar archive normally used by the Java 2 software.

Enable the incremental garbage collector. The incremental garbage collector, which is off by default, will eliminate occasional garbage-collection pauses during program execution. However, it can lead to a roughly 10% decrease in overall performance.

Operate in interpreted-only mode. Compilation to native code is disabled, and all bytecodes are executed by the interpreter. The performance benefits offered by the Java HotSpot adaptive compiler will not be present in this mode.

Set the Java new generation heap size (for example: -Xmn64m). The "new generation" is the first generation in HotSpot's generational garbage collector. This option replaces the option -XX:NewSize=N.

Specify the initial size, in bytes, of the memory allocation pool. This value must be a multiple of 1024 greater than 1MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is 5248KB. Examples:

-Xms4194304
-Xms4096k
-Xms4m

Specify the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.The default value is 64MB. Examples:

-Xmx83886080
-Xmx81920k
-Xmx80m

Disables class garbage collection.

Profiles the running program, and sends profiling data to standard output. This option is provided as a utility that is useful in program development and is not intended to be be used in production systems.

Reduces use of operating-system signals by the Java virtual machine (JVM).

Specify the size of stack for each new Java thread. The default Java thread stack size is 512 KB. This flag is appropriate for programs that have small thread stack size requirements and/or create several thousand threads, potentially running out of virtual memory. Program threads that overflow the allocated stack will receive java.lang.StackOverFlowException. Example: -Xss128k

Using this command instructs the JVM not to complain if the application installs signal handlers.

Disable calls to System.gc(). The JVM still performs garbage collection when necessary.

Sets the maximum size of new generation (in bytes). Note that in HotSpot 1.0.1 this option took an integer that specified a value in Kbytes. Starting with HotSpot 1.3.1, the integer argument specifies bytes. The arguments can now be followed by either 'k' or 'm' to specify Kbytes or Mbytes.

Sets the default size of new generation (in bytes). Note that in HotSpot 1.0.1 this option took an integer that specified a value in Kbytes. Starting with HotSpot 1.3.1, the integer argument specifies bytes. The arguments can now be followed by either 'k' or 'm' to specify Kbytes or Mbytes.

Sets the additional size added to desired new generation size per non-daemon thread (in bytes). Note that in HotSpot 1.0.1 this option took an integer that specified a value in Kbytes. Starting with HotSpot 1.3.1, the integer argument specifies bytes. The arguments can now be followed by either 'k' or 'm' to specify Kbytes or Mbytes.

Sets the maximum size of permanent generation (in bytes). Note that in HotSpot 1.0.1 this option took an integer that specified a value in Kbytes. Starting with HotSpot 1.3.1, the integer argument specifies bytes. The arguments can now be followed by either 'k' or 'm' to specify Kbytes or Mbytes.

A set of XX options which, when bundled together, make some applications run faster. For each release, the options as well as the values may be different depending upon the default values of XX options. We recommend that you test to see whether this set enhances the performance of your application before you use the option in production.

Ratio of eden/survivor space size. Default for SDK 1.3 is 64MB. Number can include 'm' or 'M' for megabytes, 'k' or 'K' for kilobytes, and 'g' or 'G' for gigabytes. For example, 32k is the same as 32768.

Use the java command line option -XX:+UseSIGUSR2 if you want the JVM to use SIGUSR2 for internal operations like Thread.interrupt() calls instead of SIGUSR1, the default. This allows you to better implement third party middleware applications that in some versions want to use SIGUSR1 for similar purposes in their native code.

java -Xeprof:<options> ApplicationClassName

appletviewer -J-Xeprof:<options> URL>

-Xeprof or

-Xeprof:ie=no

-Xint -Xeprof:ie=no

java -Xeprof:help

file=<filename>

The profile data will be written to the named file. The default is java.eprof.

Collect call graph with inclusive method clock and CPU times and method call count.

This option uses tracing with reduction and collects the data separately for each thread, throughout the whole execution time of the program.

The quick value instructs the profiler to use the hardware Interval Timer register for time measurement. This value results in faster profiling runs, but in very rare circumstances can produce inaccurate data. This is the default for PA-RISC 2.0 based machines. If you ever suspect that the profile data generated using the quick value is incorrect then redo the run to see whether the results can be replicated.

The thorough value is the opposite of quick, disabling the use of the Interval Timer. The profiling runs will be longer, but will provide timing data with the same quality as the system calls used to measure the time. However, the profiling intrusion and overhead also increase. This is the default for PA-RISC 1.1 based machines.

Enable/disable the profiling intrusion estimation.

ie=yes, the default value, specifies that the profiler estimate the profiling intrusion and write the estimated values to the profile data file. A future version of HPjmeter will be able to present the timing data as: raw, meaning the data as collected, or compensated, meaning with the estimated intrusion subtracted.

Disabling intrusion estimation reduces the size of the data files, but will also disable the intrusion compensation feature.

Disable/enable inlining in the HotSpot VM.

The compiler in the HotSpot VM optimizes Java applications by inlining frequently called methods. Execution of inlined methods does not count as "calls" from the profiler's viewpoint. Instead, the time spent in an inlined method is attributed to its caller.

The count of created objects cannot be reliably estimated in the presence of inlining, because the calls to the constructors may have been inlined.

To obtain an accurate method call count and to enable the created objects metric, run the VM with inlining=disable.

-Xprep <factory_class_name>:<arguments>

class <factory_class_name> implements Preprocessor {
  public static Preprocessor createPreprocessor (String arg)

package hp.javatools.bytecode;
public interface Preprocessor {
  public abstract byte[] instrument (String name, byte[] klass); }

%1: Indicates the cause of the garbage collection.
     -1: indicates a Scavenge (GC of New Generation only)
    0-6: indicates a Full GC (collection of all spaces in the
         Java Heap)
   Reason:
      0:  Call to System.gc
      1:  Old Generation full
      2:  Permanent Generation full
      3:  Train Generation full
      4:  Old generation expanded on last scavenge
      5:  Old generation too full to scavenge
      6:  FullGCAlot

%2: Program time at the beginning of a collection, in seconds.

%3: Garbage collection invocation. Counts of Scavenge and Full GCs are 
	maintained separately.

%4: Size of the object allocation request that forced the GC, in bytes.

%5: Tenuring threshold - determines how long the new born object remains 
	in the New Generation.

    The report includes the size of each space:
       Occupied before garbage collection (Before)
       Occupied after garbage collection (After)
       Current capacity (Capacity)

All are in bytes.

Eden sub-space (within the New Generation)
%6:  Before
%7:  After
%8:  Capacity

Survivor sub-space (within the New Generation)
%9:  Before
%10: After
%11: Capacity

Old Generation
%12: Before
%13: After
%14: Capacity

Permanent Generation (Storage of Reflective Objects)
%15: Before
%16: After
%17: Capacity

%18: Duration of the garbage collection in seconds.

java.lang.ClassCastException: sun.awt.motif.X11OffScreenImage
        at BezierAnimationPanel.run(BezierAnimationPanel.java:223)
        at java.lang.Thread.run(Unknown Source)
		

1. Install the patches you need from the list below. Install the common patch, plus the appropriate patch for your language. To download patches, go to the Patch Database at the IT Resource Center website.
   
   Select the link "Individual Patches" under Maintenance/Support. Scroll down to "retrieve a specific patch by entering the patch name" and enter the patch number in the input field. (This process will redirect you to a new patch if a patch has been superceded.) Read the information about the patch to ascertain any dependencies.
   
   

   Japanese:		PHSS_24931 (for 11.00) or PHSS_24932 (for 11i 11.11)
   Korean:		PHSS_24933 (for 11.00) or PHSS_24934 (for 11i 11.11)
   Simple-Chinese:		PHSS_24935 (for 11.00) or PHSS_24936 (for 11i 11.11)
   Common:		PHSS_25091 (for 11.00) or PHSS_25092 (for 11i 11.11)

2. Make sure you have installed HP's SDK version 1.3.1.02 or later, which supports Asian TrueType fonts, including new versions of the font.properties files.

3. Check the status of the font server. The HP-UX X Server uses X Font Server (xfs) as its TrueType font server. In some cases Java's font display may be affected by this daemon because it makes TrueType scalable fonts available.
   
   
   
   To query your X display, use the command "xset -q". This will list the X Font Path. If the path includes the X Font Server, remove it using the command "xset -fp tcp/<yourHost>:7000"

4. When your Java application runs under an Asian locale, Java fonts are defined using the following fonts.properties files shipped in $JAVA_HOME/jre/lib.
   
   

   LANG=ja_JP.SJIS		font.properties.ja
   LANG=ko_KR.eucKR		font.properties.ko
   LANG=zh_CN.hp15N		font.properties.zh_EUC_CN

/usr/bin/X11/xfs -config /etc/X11/fs/config -port 7000 -daemon
xset +fp tcp/localhost:7000

-XX:+ReduceSignalUsage

int *p = NULL;
return *p;

1. Remote debugging with the -attach or -listen jdb option.
2. You are implementing a debugger which uses the JDWP directly.
3. You are implementing a debugger back end which uses JVMDI.

-XdoCloseWithReadPending

• HP JDK 1.3.1
• Swing components
• xfs running (use xset -q to see status)
• locale (LANG) is Korean (ko_KR.eucKR) or simple Chinese (zh_CN.hp15CN)