NonStop Server for Java 7.0 Programmer's Reference

Using _RLD_FIRST_LIB_PATH
NSJ7 does not support loading of a public DLL from a non-standard private location by using
_RLD_FIRST_LIB_PATH environment variable. This limitation is due to the fact that NSJ7 creates
a group of processes that should load the public DLLs at the same virtual memory address order,
so that the parallel garbage collectors are functioned appropriately. This is unlike earlier versions
of NSJ where the entire Java application is run as a single instance of JRE/JVM process.
However, HP recommends that you must not load public libraries from private locations.
Other considerations
Default Java heap size and stack size
For 64–bit NSJ7, the default heap and stack sizes are as follows:
• The default stack size is 1024 KB.
• The initial heap size is 1 GB and the default maximum heap size is 1 GB.
For more information, see “Java heap size with 32–bit JDK7” (page 57) and “Java heap size with
64–bit JDK7” (page 57).
NOTE: HP recommends that the application specifies the same value for —Xms and —Xmx. If only
—Xmx is specified in the command-line, the default value used for —Xms is the same value that is
specified for —Xmx.
For more information, see “Memory management considerations” (page 56).
Java process name
A Java process can be started as a named process by specifying —name option with the run
command. In NSJ7, there is a restriction in starting a named Java process and it is explained in
the following subsections.
Using 32–bit JDK
A 32–bit Java application can be launched with NSJ7 by one of the following methods. However,
only the Method 1 can be used to launch 32–bit JDK as a named process.
Method 1: Using 32–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin:$PATH
$ run –name /G/JAVA1/ java HelloWorld
Method 2: Using 64–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin/oss64:$PATH
$ run –name /G/JAVA1/ java –d32 HelloWorld
NOTE: The 64–bit Java process created first in the Method 2 is a named process having name
$JAVA1. This process uses execvp() system call to create the 32–bit Java process. A process
created using execvp() does not inherit the name of the calling process, and hence the resultant
32–bit process is unnamed.
Using 64–bit JDK
A 64–bit Java application can be launched with NSJ7 by one of the following methods. However,
only the Method 2 can be used to launch 64–bit JDK as a named process.
Method 1: Using 32–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin:$PATH
$ run –name /G/JAVA1/ java –d64 HelloWorld
98 Migrating applications