InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.28: Planning and skills for IBM Distributed Debugger and OLT >
6.6.28.3: Prerequisites and limitations of IBM Distributed Debugger and OLT
6.6.28.3: Prerequisites and limitations of IBM Distributed Debugger and OLT
This article provides information about Distributed Debugger and OLT prerequisites,
and how they relate to IBM WebSphere Application Server prerequisites. It also lists
current limitations, problems, and workarounds.
Supported prerequisites
IBM Distributed Debugger and OLT are separate products bundled with IBM WebSphere
Application Server for your convenience. Because the Distributed Debugger and OLT support
for operating systems and JDK levels can differ from those supported by IBM WebSphere
Application Server, the Debugger and OLT support is summarized in the table below.
Inclusion of a prerequisite in the table does not imply that
IBM WebSphere Application Server also supports the prerequisite. Always refer to the
IBM WebSphere Application Server prerequisites to determine
which prerequisites are supported by the base Application Server product and its Fix Packs.
IBM WebSphere Application Server Release |
Operating systems supported by Debugger and OLT |
Version 3.5 base |
Remote and distributed debugging support and tracing capabilities
on JDK 1.2.2 on Windows NT, AIX, and Solaris:
- Windows NT Java debugging is supported on JDK 1.2.2
- AIX and Solaris Java debugging is supported on JDK 1.1.8
|
Version 3.5 plus Fix Pack 1 |
Remote and distributed Java
debugging support and tracing capabilities on Windows NT, AIX, and
Solaris, as follows:
- Windows NT Java debugging is supported on JDK 1.2.2
- AIX and Solaris Java debugging is supported on JDK 1.1.8
- Tracing capabilities are supported on JDK 1.2.2 on Windows NT, AIX, and Solaris
|
Version 3.5 plus Fix Pack 2 |
|
Known limitations, problems, and workarounds
Problem |
Operating systems |
Workaround (if available) |
When debugging a JSP (1.0 OR 0.91) Distributed Debugger
does not step over empty lines. For example, when stepping into a JSP like:
Line 1: Hello<BR>
Line 2:
Line 3: World!
the debugger stops at line 2. |
Windows NT |
|
The JVM arguments are not being passed to the Java program
if the user invokes idebug using the -qjvmargs option. |
AIX |
Start the OLT Viewer and place it in the Online mode. Then debug
the Java program using idebug with the -qjvmargs option as usual. |
Add irmtdbgj.exe to the nanny.path in the admin.config file for
Object Level Trace. |
|
Before running OLT/Debugger support in WebSphere Application
Server, you must add the location of the executable irmtdbgj.exe to the nanny.path variable
in the WebSphere Application Server admin.config file. For example, on Windows NT, add the
path
<drive>\IBMDebug\bin\irmtdbgj.exe
to the variable
com.ibm.ejs.sm.util.process.Nanny.path
in the WebSphere\AppServer\bin\admin.config file. |
When running the OLT Viewer, if you try to change the Execution Mode
in the Client Controller for a connected client and then click Apply, the viewer might
freeze. |
Windows 2000 |
Ensure that you have set the Execution Mode properly in the
Client Controller for the Default settings entry before you try tracing. Do not attempt
to change the Execution Mode after you start a trace. |
|
|