NonStop Server for Java 6.0 Programmer's Reference

For more details, see the Sun Microsystems Java Platform Debugger Architecture Documentation
(http://docs.oracle.com/javase/6/docs/technotes/guides/jpda/architecture.html).
JDI specification does not provide in-process debugging. Hence, a Java based tool called a
debugger is used to debug another JVM running the Java application. This JVM, called the
debuggee, also contains the back-end of the debugger that is responsible to accept the request
from the front-end of the debugger and to respond to these requests.
NonStop Server for Java 6.0 ships a terminal oriented non-GUI debugging tool. This Java Debugger
Tool (JDB) can be used on a NonStop system platform to debug the Java applications running on
the same NonStop system or on another NonStop system or any other platform.
You can also use the non-GUI debugging jdb and other vendors' GUI debuggers running on
Microsoft Windows and other platforms to debug NonStop Server for Java 6.0 applications running
on a NonStop system.
Transports
A JPDA transport is a form of inter-process communication used by a debugger application and
the debuggee. NonStop Server for Java 6.0 provides a socket transport that uses the standard
TCP/IP sockets to communicate between debugger and the debuggee.
NonStop Server for Java 6.0 defaults to socket transport. NonStop Server for Java 6.0 does not
support shared memory transport.
java Command Line Options to Run a Debuggee
For remote debugging, you need to start the Java application to be debugged (debuggee) as a
server using the following command:
java -Xdebug -Xnoagent
Debugging Java Programs 55