NonStop Server for Java 7.0 Programmer's Reference

Method 2: Using 64–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin/oss64:$PATH
$ run –name /G/JAVA1/ java HelloWorld
NOTE: The 32–bit Java process created first in the Method 1 is a named process having name
$JAVA1. This process uses execvp() system call to create the 64–bit Java process. A process
created using execvp() does not inherit the name of the calling process, and hence the resultant
64–bit process is unnamed.
Debugging Java process
A Java process can be automatically launched inside the Native Inspect debugger using —debug
command-line option with run command.
Debugging using 32–bit JDK
A 32–bit Java application can be launched inside the Native Inspect (eInspect) debugger by one
of the following two methods. However, only the Method 1 can be used to launch the process
under debug.
Method 1: Using 32–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin:$PATH
$ run –debug java HelloWorld
Method 2: Using 64–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin/oss64:$PATH
$ run –debug java –d32 HelloWorld
NOTE: The 64–bit Java process created first in the Method 2 is under einspect. As this process
uses execvp() system call to create the 32–bit Java process and a process created using
execvp() does not inherit the PIN of the calling process, eInspect cannot continue to debug the
process. If you want to debug it, a new debugger needs to be attached to the process.
Debugging using 64–bit JDK
A 64–bit Java application can be launched inside the Native Inspect (eInspect) debugger by one
of the following two methods. However, only the Method 2 can be used to launch the process
under debug.
Method 1: Using 32–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin:$PATH
$ run –debug java –d64 HelloWorld
Method 2: Using 64–bit JDK
$ export PATH=/usr/tandem/nssjava/jdk170_h70/bin/oss64:$PATH
$ run –debug java HelloWorld
NOTE: The 32–bit Java process created first in the Method 1 is under einspect. As this process
uses execvp() system call to create the 64–bit Java process and a process created using
execvp() does not inherit the PIN of the calling process, eInspect cannot continue to debug the
process. If you want to debug it, a new debugger needs to be attached to the process.
Other considerations 99