OLT troubleshooting - Installation and startup

Cannot open input stream for dertrdf1
This message will usually appear in the command prompt during a command-line start of OLT. It can be ignored.

"Cannot copy ivbtr30i.dll"
If you receive this message on a new install of the IBM Distributed Debugger, and you have Component Broker already installed, stop all servers, orb daemons, and bgmain, then retry the installation.

OLT server or viewer fails to start
If OLT appears to start, then closes prematurely, try starting from the command line by typing olt. If the problem persists, go in the ngwin.gif (301 bytes)%userprofile%\dbgprof directory (ngaix.gif (307 bytes)$HOME/.DbgProf directory) and delete all the files in this directory. Restart OLT.

This should provide you with an error message. Ensure that the directory defined by the %DER_DRIVER_PATH%\temp exists, and that you have "write" permission for this directory. If the problem persists, enter the following command to pipe your error message to a file, then send this file to your IBM representative:

olt >olt.log 2>&1

OLT viewer throws java.lang.OutOf Memory error during startup
If, when starting OLT from a command line, you see a java.lang.OutOfMemory error, you will need to edit the file that starts OLT and increase the -mx value in the file. On Windows, the file is %DER_DRIVER_PATH%\bin\olt.bat. On AIX, the file is /usr/idebug/bin/olt.

Client application fails to run
Try running the application from a command shell. If the application fails to start, a detailed error message should appear. (For help interpreting the message, Component Broker users should see the Problem Determination Guide).

Client application runs, but OLT appears to stop the application server
Check the transaction timeout values in your application code. These values must be set to zero, or a value not easily reached while using the debugger, such as 300 seconds.

Events do not appear in the viewer
If your application runs cleanly, but events do not appear in the OLT viewer, ensure that you have completed the necessary startup steps:

  1. For Enterprise Business Objects, build your code using OLT flags.
  2. If using WebSphere Enterprise Edition (Component Broker), enable OLT in System Manager user interface by selecting the Enable debug checkbox in both the Client Style and Server Images.

    If using WebSphere Advanced Edition, ensure that OLT is enabled in the Admin Console.

  3. Start OLT (on Windows systems, do not close the OLT command prompt window).
  4. Run your client application.

For detailed instructions, see the topic "Preparing for an OLT and IBM Distributed Debugger session".

Unusual program behavior
Check your temporary directory (as set by the %DER_DRIVER_PATH%/TEMP environment variable on Windows NT/2000, or the /tmp directory on AIX). If you have a .chk file in your temporary directory, delete it and try running your application again. During normal operation, Object Level Trace creates files in the temporary directory and, if the program terminates unexpectedly, some of these files may not be properly deleted.

OLT/DD cannot grab the focus on Windows 2000
The application window has problems grabbing focus (Windows 2000 only, possibly Windows ME). When a window that does not have the focus (in the background) is updated by its program, Windows 2000, by default, prevents it from becoming the topmost window. Instead Windows 2000 flashes the taskbar button. This behavior is governed by the DWORD [REG_DWORD] values which you can change by running Regedit (or Regedt32) and going to HKEY_CURRENT_USER\Control Panel\Desktop to modify DWORD [REG_DWORD] settings, as follows:

Remote DHCP-enabled host running OLT and the Distributed Debugger
For WebSphere Advanced Edition only. If a DHCP-enabled host is running OLT and the Distributed Debugger on a WebSphere application which is residing on a remote host and the DHCP host's IP address changes (for example, as a result of rebooting the host), then you may experience difficulty in re-running the WebSphere application using OLT and the Distributed Debugger. This problem occurs because your previous IP address has been cached by the remote JVM which is running the WebSphere Application Server.

This problem is avoidable. If there is a possibility that applications residing on a WebSphere Application Server are going to be traced and debugged remotely using OLT and the Distributed Debugger that are running on DHCP-enabled hosts, then you may want to consider adding the following argument to your AppServer command :

-Dsun.net.inetaddr.ttl=0 

Setting this argument to 0 informs the JVM that is running the WebSphere Application Server not to cache IP addresses. Thus the DHCP hostnames (whose IP addresses are constantly changing) are not mapped to one-time fixed IP addresses by the JVM. In addition to setting this argument, if the WebSphere Application Server itself resides on a DHCP-enabled host, Windows users may also need to disable the DNS Client service, to prevent the operating system from caching the IP addresses.

ngrelt.gif (466 bytes)
Preparing for an OLT and IBM Distributed Debugger session

ngrelr.gif (548 bytes)
Troubleshooting