Transaction Tracking API troubleshooting

Errors encountered in Transaction Tracking API are generally from incorrect settings.

Common problems

If you encounter difficulties, check the following problem for Transaction Tracking API first:

  • When ARM Transaction Tracking API logging is enabled, WebSphere is restarted after the log size reaches 2 GB. To avoid this, use the RAS1 logging configuration to set the maximum log file size to a value lower than 2 GB, such as 1 GB.
  • When compiling an ARM-instrumented application on HP-UX systems, ensure that the application is compiled in multi-threaded mode.
Parent topic: Transaction Tracking troubleshooting