The ABL object tracking APIs can be used to find memory leaks in ABL code on a PAS for OpenEdge instance. These APIs are an improvement over the previous method of tracking ABL objects, which required enabling the DynObjects log entry types and creating a LOG-MANAGER (-clientlog) system handle. This method produced a complex log file that had to be manually searched for memory leaks.

The benefits of using the ABL object tracking APIs to find memory leaks in PAS for OpenEdge are that:
  • You can turn the functionality on and off interactively, so there is no reason to shut down a production application to make logging changes.
  • The APIs show memory leaks only, rather than making additional calls to the log file for Dynamic Objects.
  • The APIs result in less, if any, server slow-down than in the previous method of using Dynamic Objects, and can be turned off interactively to limit performance costs.
To use ABL object tracking to identify memory leaks in a running PAS for OpenEdge instance:
# Steps Using the REST API Using the OEJMX API
1 Enable ABL object tracking. Enable or disable ABL object tracking. Enable or disable ABL object tracking query.
2 Verify the ABL object tracking status is enabled. Check ABL object tracking status. Check ABL object tracking status.
3 Continue to let the application operate with ABL object tracking enabled. Blank Blank
4 Generate a report of the tracked ABL objects. Get a report of tracked ABL objects. Get a report of tracked ABL objects query.
5 Disable ABL object tracking after leaks have been identified and resolved. Enable or disable ABL object tracking. Enable or disable ABL object tracking query.