Feedback
Did this article resolve your question/issue?

   

Article

ABL Objects Tracking REST API under PASOE

« Go Back

Information

 
TitleABL Objects Tracking REST API under PASOE
URL NameNew-ABL-Objects-Tracking-REST-API-under-PASOE
Article Number000123507
EnvironmentProduct: OpenEdge
Version: 11.7.3, 11.7.4, 11.7.5
OS: All Supported Platforms
Question/Problem Description
ABL Object Tracking allows tracking application memory leaks using PASOE's REST API similar to DynObjects client logging
In OpenEdge 11.7.3 Progress AppServer for OpenEdge provides the ability to turn on ABL Object Tracking
In OpenEdge 11.7.4 the ABL Object Tracking APIs are replaced by updated APIs



 
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
​In previous versions of the product, in order to track memory leaks in an ABL application, the DynObjects.* log entry type in conjunction with the LOG-MANAGER (-clientlog) is used to generate a potentially ungainly log file which would then have to be interpreted to find potential memory leaks in the executed ABL code.

OpenEdge 11.7.3 introduced a *NEW* REST API to track memory leaks in ABL application code used by a PAS ABL Session. In 11.7.4 further updates were provided in the API. 

To use ABL Object Tracking:
  • HTTP Operation
GET 
 
  • Turn on ABLObjects tracking
URI
(11.7.3) http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/trackABLObjects/true

(11.7.4) HTTP Operation: PUT
http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/ABLObjects/status

Body
{ "enable":"true"}

header
Content-Type : application/vnd.progress+json
 

  • Check ABLObject tracking status
URI
(11.7.3) http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/trackingABLObjects

(11.7.4) http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/ABLObjects/status
  • Get ABLObjectsReport
URI
(11.7.3) http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/getABLObjectsReport

(11.7.4) http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/ABLObjects
  • Turn off ABLObjects tracking
URI
(11.7.3) http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/trackABLObjects/false
 
(11.7.4) HTTP Operation: PUT
http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/ABLObjects/status

Body
{ "enable":"false"}

header
Content-Type : application/vnd.progress+json


Example:
  1. Turn on tracking:
http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/trackABLObjects/true
{
"result": true,
"operation": "TRACKING ABL OBJECTS",
"versionStr": "v11.7.3 ( 2018-04-27 )",
"versionNo": 1,
"outcome": "SUCCESS",
"errmsg": ""
}
  1. Check tracking status
http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/trackingABLObjects
{
"result": true,
"operation": "TRACKING ABL OBJECTS",
"versionStr": "v11.7.3 ( 2018-04-27 )",
"versionNo": 1,
"outcome": "SUCCESS",
"errmsg": ""
}
  1. Get ABLObjectsReport
http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/getABLObjectsReport
(Below is sample output, not complete)
{
"result": {
"ABLOutput": {
"ABLObjects": [
{
"AgentSessionId": 4,
"Objects": []
},
{
"AgentSessionId": 7,
"Objects": [
{
"ObjType": "MEMPTR",
"HandleId": 1038,
"Size": 1024,
"Source": "RunleakCode.p",
"Line": 52
},
{
"ObjType": "MEMPTR",
"HandleId": 1037,
"Size": 1024,
"Source": "RunleakCode.p",
"Line": 52
},
  1. Turn off tracking
http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/trackABLObjects/false
  1. Check tracking status
http(s)://<hostName>:<port>/oemanager/applications/<app_name>/agents/<agentPID>/trackingABLObjects
{
"result": false,
"operation": "TRACKING ABL OBJECTS",
"versionStr": "v11.7.3 ( 2018-04-27 )",
"versionNo": 1,
"outcome": "SUCCESS",
"errmsg": ""
}

Code examples to use the ABL HttpClient libraries to interact with this API are available in the following Article:
Workaround
Notes
References to Other Documentation:

APIs are documented in the 11.7.4 OpenEdge® Service Pack: New Information document. A copy of this PDF is attached below.

Progress Article:
Program for viewing and filtering PASOE REST API's ABLObjects output
Identifying and Troubleshooting Memory Leaks
 
Last Modified Date1/22/2021 1:17 PM
Attachment 
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.