HP-UX 11i Java™ JDK/JRE Version 6.0.22 Release Notes

session below shows that the crash occurred in Hashtable::put while executing the
fast_igetfield function:
> (gdb) bt
> ...
> #7 0x60000000cc4ad4a0:0 in os::Hpux::signalHandler ()
> #8 <signal handler called>
> #9 0x200000007ac25c01 in interpreted frame: java.util.Hashtable::put
> (java.lang.Object, java.lang.Object) ->java.lang.Object bci: 166
> ...
> (gdb) frame 9
> #9 0x200000007ac25c01 in interpreted frame: java.util.Hashtable::put
> (java.lang.Object, java.lang.Object) ->java.lang.Object bci: 166
> (gdb) info frame
> ...
> Java interpreted frame specific info:
> ...
> bytecode pointer: 0x3682e0be, bytecode: fast_igetfield
> ...
To determine if hyperthreading is enabled, run the setboot system command:
setboot
To disable hyperthreading, change the boot parameter and reboot the system:
setboot -m off
reboot
To work around the crash with hyperthreading enabled, use the option:
-XX:-RewriteBytecodes
Invoking jstat or jps on java_q3p/java_q4p on PA-RISC
Problem:
The java launcher invokes different executables depending on the heap size specified
on the command line. On PA-RISC, there are 3 possible executables, java, java_q3p,
and java_q4p. Attempting to connect to the java_q3p executable using the jstat
command can result in an error:
Exception in thread "main" java.lang.OutOfMemoryError: Could not map PerfMemory
Attempting to connect to the java_q3p executable using the jps command can result
in the following:
<pid> -- process information unavailable
Workaround:
To work around this problem, you can chatr the jps and jstat executables to enable
q3p:
cd <java location>/bin/PA_RISC2.0
cp jps jps_q3p
chatr +q3p enable jps_q3p
Known issues 19