Java commands: Starting the Debugger engine remotely
Before you issue the irmtdbgj command described in this section, ensure that you have
started the debugger user interface daemon on your remote workstation with the following
idebug command:
idebug -qdaemon -quiport=8001
irmtdbgj -qhost=<Hostname> -quiport=<ui_daemon_port>
-jvmargs="-nojit
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.requestTimeout=0
-Dcom.ibm.CORBA.BootstrapHost=<BootstrapHostname>
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true"
-classpath "<path\YourAppJarFile>;
<path\somojor.zip>;<path\dertrjrt.jar>;%CLASSPATH%" AppName
Variation for AIX:
- Remove the -nojit option
- Replace %CLASSPATH% with $CLASSPATH
where:
- See the irmtdbgj command in the debugger
information for a description of the irmtdbgj parameters.
- See Supported Java Virtual Machine arguments
in the debugger documentation for additional information.
- <Hostname> = the IP address or name of the machine where the
user interface daemon is running
- <ui_daemon_port> = the TCP/IP port used for the connection.
The default port is 8001.
- <BootstrapHostname> = For Component Broker only. This is your
fully qualified server application host name (only needed if System Manager is running on
a different host)
- <OLT_Server_Host> = the fully qualified name or TCP/IP address
of the machine running your OLT server
- <OLT_Server_Port> = the port where the OLT server listens for
connecting OLT Runtimes. The default is 2102.
- <path\somojor.zip> = x:\CBroker\lib\somojor.zip on Windows NT/2000;
/usr/lpp/CBConnector/lib/somojor.zip on AIX; /opt/WebSphere/AppServer/lib/dertrjrt.jar on
Solaris.
- <path\dertrjrt.jar> = x:\WebSphere\AppServer\lib\dertrjrt.jar
on Windows NT/2000; /usr/WebSphere/AppServer/lib/dertrjrt.jar on AIX;
/opt/WebSphere/AppServer/lib/dertrjrt.jar on Solaris, /opt/IBMcbc/lib/dertrjrt.jar on
OS/390.
- AppName is the fully qualified path to your program.
Notes
- In the classpath option, the path required is not
necessarily the same for each occurrence in the option. That is, there may be different
paths to the .jar and .zip files.
- <BootstrapHostname> is applicable only for WebSphere
Application Server, Enterprise Edition.
Additional comments
- If you attach the Debugger to your Java client application, the Debugger takes control
of the stdin and stdout of the Java client application.
- Known JDK limitation: If you attach the Java debugger to your Java client application,
you must Ctrl+C the client application when it terminates.
- When running your debugger remotely and the source files reside on the machine where you
are running the debugger user interface, set DER_DBG_PATH environment variable to include
your source files.
- When debugging remotely using the irmtdbgj command in Windows NT/2000, if the -classpath
value that is passed to the -jvmargs option has a space, the debugger will not be able to
launch a JVM for the application. To avoid this problem you can do one of the following:
For the Java 2 platform:
irmtdbgj -qhost=<Hostname> -quiport=<ui_daemon_port>
-jvmargs="-Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<JVM_port>
-Djava.compiler=NONE
-Xbootclasspath/a:"<WebSphere_jdk>\lib\tools.jar;<WebSphere>\lib\derdbpw.jar"
-classpath "<your_app_jars>;<WebSphere>\lib\dertrjrt.jar;%CLASSPATH%"
-Dcom.ibm.debug.jdwpport=<JVM_port>
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.requestTimeout=0
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true" AppName
Variation for AIX:
- Replace %CLASSPATH% with $CLASSPATH
where:
- See the irmtdbgj command in the debugger
information for a description of the irmtdbgj parameters.
- See Supported Java Virtual Machine arguments
in the debugger documentation for additional information.
- <Hostname> = the IP address or name of the machine where the
user interface daemon is running
- <ui_daemon_port> = the TCP/IP port used for the connection.
The default port is 8001.
- <OLT_Server_Host> = the fully qualified name or TCP/IP address
of the machine running your OLT server
- <OLT_Server_Port> = the port where the OLT server listens for
connecting OLT Runtimes. The default is 2102.
- AppName is the fully qualified path to your program.
Notes
- In the classpath option, the path required is not
necessarily the same for each occurrence in the option. That is, there may be different
paths to the .jar and .zip files.
- When running your debugger remotely and the source files reside on the machine where you
are running the debugger user interface, set DER_DBG_PATH environment variable to include
your source files.
- When debugging remotely using the irmtdbgj command in Windows NT/2000, if the -classpath
value that is passed to the -jvmargs option has a space, the debugger will not be able to
launch a JVM for the application. To avoid this problem you can do one of the following:
irmtdbgj -qhost=<Hostname> -quiport=<ui_daemon_port>
-jvmargs="-Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<JVM_port>
-Djava.compiler=NONE
-Xbootclasspath/a:"<WebSphere_jdk>\lib\tools.jar"
-classpath "<your_app_jars>;<WebSphere>\lib\dertrjrt.jar;%CLASSPATH%"
-Dcom.ibm.debug.jdwpport=<JVM_port>
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.requestTimeout=0
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true" AppName
Variation for AIX:
- Replace %CLASSPATH% with $CLASSPATH
where:
- See the irmtdbgj command in the debugger
information for a description of the irmtdbgj parameters.
- See Supported Java Virtual Machine arguments
in the debugger documentation for additional information.
- <Hostname> = the IP address or name of the machine where the
user interface daemon is running
- <ui_daemon_port> = the TCP/IP port used for the connection.
The default port is 8001.
- <OLT_Server_Host> = the fully qualified name or TCP/IP address
of the machine running your OLT server
- <OLT_Server_Port> = the port where the OLT server listens for
connecting OLT Runtimes. The default is 2102.
- AppName is the fully qualified path to your program.
Note:
- When running your debugger remotely and the source files reside on the machine where you
are running the debugger user interface, set DER_DBG_PATH environment variable to include
your source files.
- When debugging remotely using the irmtdbgj command in Windows NT/2000, if the -classpath
value that is passed to the -jvmargs option has a space, the debugger will not be able to
launch a JVM for the application. To avoid this problem you can do one of the following:

Debugging from a remote workstation

Java commands for tracing and debugging