Debugging a Probe
Debugging a Probe
This article provides information about debugging a probe.
Resources for Debugging a Probe
To debug a probe, you can:
- Look at log files generated by a probe. Select theView Logoption in Admin Console.
- Use Dr.NimBUS, provided with CA UIM, to watch data on the UIM message bus.
- Attach a Java debugger to a probe to step through the code.
Attaching a Java Debugger to a Probe
You can debug a probe using the IDE of your choice in exactly the same manner as you would debug any other Java program. The key to debugging any Java program is to pass the debug specific parameters as command line arguments to the JVM when the Java program is started.
You can find a probe's command line arguments in its .cfg file in the 'startup' section:
<setup> loglevel = 3 </setup> <startup> options = -Xms32m -Xmx512m -Duser.language=en -Duser.country=US </startup> ...
Any parameters that you need to pass to the JVM for debugging should be appended to the startup options already present in the .cfg file. For example, to perform a debug session on port 1044 you would append the options:
<setup> loglevel = 3 </setup> <startup> options = -Xms32m -Xmx512m -Duser.language=en -Duser.country=US -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044 </startup>
Following these steps to debug a probe that is running on a robot.
- Stop the probe.
- Append the following to the <Startup> options in the deployed <probe>.cfg file:-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<port_to_use>The probe install directory is in the C:\Program Files (x86)\Nimsoft\probes directory.
- Restart the probe.
- Using your favorite IDE, attach its debugger using the robots IP address and the port you specified in the <probe>.cfg file.