Did this article resolve your question/issue?



Detect PASOE memory leaks with Dynamic Objects Logging

« Go Back


TitleDetect PASOE memory leaks with Dynamic Objects Logging
URL NameDetect-PASOE-memory-leaks-with-Dynamic-Objects-Logging
Article Number000127146
EnvironmentProduct: OpenEdge
Version: 11.7.x
OS: All supported platforms
Other: PASOE
Question/Problem Description
Detect PASOE memory leaks with Dynamic Objects Logging 
How to detect ABL Memory Leaks with Dynamic Objects Logging for PASOE
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Adjust the the application logging then run the attached ABL leakcheckPASOE.p code to identify object leaks.

1. Stop the PASOE instance, if it's running.
2. Configuring the PASOE multi-session agent for which type of logging and how verbose it logs the information in:



3. Start the PASOE instance to allow the new entries to be used.

$  pasman pasoestart restart -I <alias>

4. Run the test for a short period of time, but long enough to exercise load and multiple requests per session.

5. Extract to a folder and run the leakcheckPASOE.p to identify object leaks.

6. Review the 'report.txt' output.
Last Modified Date4/17/2019 10:20 AM
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.