Java on HP-UX 11i Frequently Asked Questions

HP performs the same functions on the Java reference implementations that we receive
from Oracle. Consequently, HP and other licensees have the opportunity to release
their products at the same time as the Solaris product from Oracle. In some cases HP
has delivered the product before IBM and before Oracle's comparable Solaris product
and with higher performance (measured by the industry standard SPECjvm98
benchmark) than either Oracle or IBM.
Q: Where can I get examples of JNI functions using parameters?
A: See the example on the following web site:
Advanced programming for the Java 2 platform
Q: Can I use RSA signed applets with the Java Plug-in on HP-UX?
A: Version 1.3 and later of the Java Plug-in supports RSA signed applets.
Troubleshooting questions
Q: When I run swlist -f sdk14_14207_1100.depot I get the following error
message: ERROR: Could not read input file "sdk14_14207_1100.depot" ERROR:
Command line parsing failed
A: Try your swlist command with an absolute path to the downloaded .depot file
and using the -s flag, as follows:
swlist -s /tmp/sdk14_14207_1100.depot
Q: I would like to find out more about the garbage collection mechanism and need
further information to understand the result of the log file generated with the
-Xverbosegc option.
A: The -Xverbosegc option is explained in detail in the “HotSpot Technology Tools
and Commands” section of the HP-UX Programmer's Guide for Java 2. In addition, you
could use HPjtune, HP's garbage collection analysis tool, that can be downloaded free
from the Software Depot HPjtune Downloads and Documentation page.
Q: My application runs a monthly batch job. The job completes successfully for smaller
numbers of records, but the process runs out of memory when it encounters records in
excess of 100000. What probable location should I start looking at for debugging?
A: There are many things that could cause this. As a start you should use HP OpenView
GlancePlus available from http://www.managementsoftware.hp.com/products/a-z.html
to find out what area the process runs out of space. If it is Java heap, run the profiler
and verbosegc to analyze the heap. For more information on verbosegc, refer to the
HP-UX Java Programmer's Guide If the problem is in the C heap (DATA) you may have
a memory leak. You can use gdb (available from www.hp.com/go/wdb) to locate the
problem. Q: Are gdb's capabilities for debugging Java documented
10