NonStop Server for Java 4.2 Programmer's Reference

While the Sun Microsystems documentation for the reference implementation states that you must set the system
property –Djava.awt.headless=true to run a headless JVM, setting this system property is unnecessary
for NonStop Server for Java 4.
ThreadDumpPath support
By default, sending the Java process a SIGQUIT signal results in a thread dump being written to stdout.
Starting with the T2766H10^ABV release, the -XX:ThreadDumpPath=<path/filename> option can be
used to specify the thread dump file name or directory where the thread dump is created.
Additional Files
In addition to the standard Java packages, the NonStop Server for Java 4 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
BaseLibList (TNS/R only)
File used to create JavaLibList, which you can use at run time to determine whether an
UnsatisfiedLinkError will be thrown during a call to System.loadLibrary, if the library was
not linked in.
Additional Environment Variable
NonStop Server for Java 4 has an implementation-specific environment variable that you can use to control the
run-time 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 detailed
information, see Controlling Maximum Concurrent Transactions.
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 4 supports JNI and the Invocation API with the following
modifications:
On TNS/R systems, you must relink the java executable whenever you use new C or C++ routines in your
Java programs.
●