Java commands: Debugging a Java client from startup
idebug -qlang=java -qjvmargs="-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:
- <BootstrapHostname> is only needed for WebSphere Application
Server, Enterprise Edition.
- <OLT_Server_Host> is the fully qualified name or TCP/IP
address of the machine running your OLT server
- <OLT_Server_Port> is the port where the OLT server
listens for connecting OLT clients. The default is 2102.
- 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.
- AppName is the fully qualified path to your program.
Notes
- See the idebug command in the debugger
documentation for a description of the idebug parameters.
- See Supported Java Virtual Machine arguments
in the debugger documentation for additional information.
- 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 press Ctrl+C to terminate the JVM in the client application.
- 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 idebug 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:
idebug -qlang=java -qjvmargs="-Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=<JVM_port>
-Djava.compiler=NONE
-Xbootclasspath/a:"<WebSphere_jdk>\lib\tools.jar;<WebSphere>\lib\derdbpw.jar"
-classpath "<path\YourAppJarFile>;<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 idebug command in the debugger
documentation for a description of the idebug parameters.
- See Supported Java Virtual Machine arguments
in the debugger documentation for additional information.
- <JVM_port> is the port for the JVM. It is a free port
number.
- <WebSphere_jdk> is the where the WebSphere JDK is
installed, for example, c:\WebSphere\AppServer\java.
- <WebSphere> is the where the WebSphere AppServer is
installed.
- <OLT_Server_Host> is the fully qualified name or TCP/IP
address of the machine running your OLT server.
- <OLT_Server_Port> is the port where the OLT server
listens for connecting OLT clients. The default is 2102.
- AppName is the fully qualified path to your program.
Notes
- -Dcom.ibm.CORBA.BootstrapHost= is applicable only for WebSphere Application
Server, Enterprise Edition.
- 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 idebug 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:
idebug -qlang=java -qjvmargs="-Xbootclasspath/a:"<WebSphere_jdk>\lib\tools.jar;"
-Djava.compiler=NONE
-classpath "<path\YourAppJarFile>;<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 idebug command in the debugger
documentation for a description of the idebug parameters.
- See Supported Java Virtual Machine arguments
in the debugger documentation for additional information.
- <WebSphere_jdk> is the where the WebSphere JDK is
installed, for example, c:\WebSphere\AppServer\java.
- <WebSphere> is the where the WebSphere AppServer is
installed.
- <JVM_port> is the port for the JVM. It is a free port
number.
- <OLT_Server_Host> is the fully qualified name or TCP/IP
address of the machine running your OLT server.
- <OLT_Server_Port> is the port where the OLT server
listens for connecting OLT clients. 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 idebug 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 client applications from startup

Java commands for tracing and debugging