NonStop Server for Java 6.0 Programmer's Reference

The following Java SE features are not applicable (and, therefore, not available):
• Class data sharing (CDS), a feature intended to reduce application startup time and footprint,
that is available only with a Java HotSpot client VM.
• Server-class machine detection because a server-class machine is always assumed
• Java user-interface features because they are desktop related
General deployment features, such as klist◦
◦ Java Web Start Technology
◦ Sound Java API
Additional Files
In addition to the standard Java packages, the NonStop Server for Java 6.0 provides these files:
jtatmf.jar
File containing classes for the version of the NonStop Java Transaction Agent that
uses TMF.
javachk
The Java Checker program, which determines whether a problem with the JVM is
caused by an incorrect TCP/IP configuration.
Additional Environment Variable
NonStop Server for Java 6.0 has an implementation-specific environment variable that you can
use to control the runtime environment. The JAVA_PTHREAD_MAX_TRANSACTIONS environment
variable specifies the maximum number of TMF transactions allowed per process. The default
number allowed is 1000. For more information, see “Controlling Maximum Concurrent Transactions”
(page 72).
Java Native Interface (JNI)
The Sun Microsystems Java Native Interface (JNI) standard defines both the C-language APIs that
enable Java methods to call C and C++ methods and the way that C and C++ methods can start
and interact with a Java Virtual Machine (JVM). The NonStop Server for Java 6.0 supports JNI
and the Invocation API with the following modifications:
• Set the _RLD_LIB_PATH environment variable to point the location of the user DLLs.
export _RLD_LIB_PATH=dll-path[:dll_pathn]...
where: dll-path and dll-pathn are the directories where the user DLLs reside.
For example, if the user DLLs are in the directory /home/mydll
export _RLD_LIB_PATH=/home/mydll
• Multithreaded native C or C++ routines must use the same Pthread library that the JVM uses,
but HP recommends that any multithreaded code be written in Java.
• If native C or C++ routines must invoke Transaction Management Facility (TMF) calls, you
must use TMF transaction jacket routines as described in the Open System Services
Programmer's Guide in the "Application Programming With Standard POSIX Threads" section
under the topic "TMF Transaction Jacket Routines." The calls are:
◦ SPT_ABORTTRANSACTION()
◦ SPT_BEGINTRANSACTION()
Additional Files 43