HP-UX Java™ SDK Version 1.3.1.08 Release Notes

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.

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

Note: To install the software into an alternate location, see
"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.

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:

If you want your Java home directory in <alternatedirectory> without the /opt/java1.3 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.

Note that we are testing another method of installing into an alternate location using <tag>. When we are confident that this method works with software depot install, we will post instructions here.

  java1.3
     |
  ___|_____________________________________________________
   |        |        |         |           |          |    
  bin      lib      jre      src.jar      demo     include 
   |        |        |
  java    tools.jar  |
  javac   dt.jar     |
  javadoc ir.idl     |
  javah   orb.idl    |
  javap              | 
  jdb                |
                  ___|__________
                     |          |
                    bin        lib
                     |          |
   __________________|______     __|_____________________________________
   |       |       |      |        |         |     |         |         |
java PA_RISC PA_RISC2  IA64     rt.jar security PA_RISC PA_RISC2.0   IA64
       ___|___ ___|_______|__   il8n.jar      _____|__  __|_____     ___|_____ 
          |       |       |                    |     |   |   |        |     |    
      native   native  native              classic HS* classic HS* classic HS*
      threads  threads threads                                         
          |       |       |
        java    java    java
					H*  = hotspot

-Xbootclasspath:<bootclasspath>

-Xms<size>

-Xss<size>

-XX:MaxNewSize=<size> (not supported on 1.3)

-XX:NewSize=<size>

-XX:NewSizeThreadIncrease=<sizeInKb>

-XX:SurvivorRatio=<size>

1: Indicates the cause of the garbage collection.
    -1: indicates a scavenge (during a scavenge only objects from
        the New space are collected)
    0-6: indicates a full garbage collection (during a full garbage
         collection objects from all areas are collected)
The code indicates the reason for the full garbage collection as follows:
    Reason:
    0:  Call to System.gc()
        The call was made by the application.
    1:  Old Generation full
        An object was to be allocated in the Old Generation, but there
        was no room there.
    2:  Permanent Generation full
        The heap area holding the reflection objects (representing Java
        classes and methods) was full.
    3:  Train Generation full
        Reserved for Java Virtual Machine developers
    4:  Old generation expanded on last scavenge
        Due to implementation reasons, if the Old Generation expanded
        on last scavenge, no more scavenges can be performed reliably
        before the next full garbage collection.
    5:  Old generation too full to scavenge
        An object was to be allocated in the New Generation, but there
        was no room there.  However, the VM has determined that the Old
        Generation was likely too full for a scavenge to compete without
        expanding the Old Generation.  Therefore a full garbage collection
        was performed rather than a scavenge.
    6:  FullGCAlot
        Reserved for Java Virtual Machine developers.
%2: The time elapsed between the Java program start and the start of this
    garbage collection event.
%3: Garbage collection invocation. This is the sequential number (count) of the
    garbage collection event. 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.

»	Download the latest Adobe® Acrobat® Reader

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.