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

libjvm.so no longer links with libstd_v2.so
Starting with JDK 6.0.07, the libjvm.so library is no longer linked with
libstd_v2.so. The intent was to reduce the chance of incompatibility when using JNI
code compiled with a C++ compiler other than aCC. However, applications that
previously relied on libjvm.so being linked with libstd_v2.so might encounter an
UnsatsifiedLinkError for an unsatisfied symbol. To solve this, the application will need to
link with libstd_v2.so directly.
Recommend setting PTHREAD_SUSPEND_SYNC to 1 under certain conditions (HP-UX
11.31 (11i v3))
If on your 11.31 system you run Java programs with either the
PTHREAD_FORCE_SCOPE_SYSTEM or PTHREAD_COMPAT_MODE environment variable
set to 1, or with the option -XX:+UseBoundThread, then setting the environment
variable PTHREAD_SUSPEND_SYNC to 1 is strongly recommended. Please see the
pthread_suspend manpage for more details.
Supplementary characters display as empty boxes
Supplementary characters are not part of the HP-UX default TrueType fonts; therefore,
they will not be available. If you try to display supplementary characters in Java 7, empty
boxes will be displayed. You may use your own fonts to display supplementary characters,
but you will need to edit the fontconfig.properties accordingly. For more information on
editing font configuration files, refer to http://download.oracle.com/javase/1.5.0/
docs/guide/intl/fontconfig.html.
Initializing a JVM instance with JNI_CreateJavaVM() or attaching to JVM with
AttachCurrentThread() on HP Integrity
The Java 7.0 stack size required to initialize a JVM instance with JNI_CreateJavaVM()
or to attach to JVM with AttachCurrentThread() is greater than the HP-UX 11.23
and 11.31 (11i v2 and v3) HP Integrity pthread default of 256 KB. If you wish to call
JNI_CreateJavaVM() or AttachCurrentThread() from a pthread, you need to
create the pthread with a larger stack size, at least 512 KB. Stack overflow failures
during JVM initialization are not always clearly reported as such, since the JVM may not
have yet installed its handlers, and the failures may appear as random exceptions. The
solution is make sure you have enough stack space.
Using linker option +noenvvar and +compat
If your application links with libjvm and uses the JNI interface APIs to load the JVM
directly, do not use the linker options +noenvvar or +compat.
Running Java with setuid or setgid on HP Integrity Systems
Running Java from setuid/setgid executables is restricted on HP-UX. In previous
HP-UX releases, executing Java from a setuid/setgid environment was not allowed.
Known issues 21