NonStop Server for Java 7.0 Programmer's Reference

_RLD_LIB_PATH
The _RLD_LIB_PATH environment variable specifies the library path for DLLs. You need to use
this environment variable if you use user DLLs. You can specify one or more directories as required.
Separate each directory in the list by using a colon (:). Set this environment variable as follows:
export _RLD_LIB_PATH=dll_path[:dll_pathn]...
where,
dll-path and dll-pathn are the directories where the user DLLs reside.
For example,
export _RLD_LIB_PATH=/home/me/mydll
Symbolic link
NSJ7 is installed in a default directory. The default directory is unique for each release, and is of
the following format:
/usr/tandem/nssjava/jdk<x>_h<yy>
where,
• x refers to the version number of Oracle Java update
• yy refers to the product version of NonStop Server for Java
For example, for NSJ7, based on Java SE 1.7.0, the installation directory is:
/usr/tandem/nssjava/jdk170_h70.
For ease of reference, a symbolic link /usr/tandem/java was being created to point to the
installation directory as a part of JDK installation in Java versions released prior to NSJ7.
Since, NSJ7 is installed and managed using DSM/SCM, the installation of NSJ7 does not
automatically create the symbolic link (soft link) /usr/tandem/java to point to the NSJ7
installation directory (/usr/tandem/nssjava/jdk170_h70). You must create the soft link
manually if required.
Configuring TCP/IP and DNS for RMI
TCP/IP and its components along with DNS must be configured properly. This has to be done for
Remote Method Invocation (RMI) to function.
A network administrator usually configures TCP/IP and DNS, but you can determine if an incorrect
TCP/IP configuration is causing a JVM problem. To check the TCP/IP configuration, use the Java
Checker (javachk) which is available in the /usr/tandem/nssjava/jdk170_h70/install
directory. Execute javachk in the same environment as JVM (that is, using the same defines that
were used to run the JVM). The javachk identifies failing socket routine calls. When you know
which calls are failing, you can troubleshoot the problems.
For information about javachk, see file
/usr/tandem/nssjava/jdk170_h70/install/README_javachk.
Memory considerations: Moving QIO to KSEG2
In NSJ7, the memory for Java heap and JVM memory is allocated from flat segments. The effects
of this memory allocation for 32–bit and 64–bit JDKs are as follows:
• For 32–bit application the flat segments are allocated from the end of the user allocatable
space. Hence the QIO segment must be moved to KSEG2 region if the memory requirement
of the Java process cannot be met with the available user memory. If the application gets out
of memory error, QIO segment must be moved to KSEG2 region.
• For 64–bit application the flat segments are allocated from the 64–bit space and hence QIO
segment need not be moved to KSEG2 region.
26 Installation and configuration