Did this article resolve your question/issue?



TempTableCount property shows number of active temp-tables increasing when using HttpClient class to post to a web api.

« Go Back


TitleTempTableCount property shows number of active temp-tables increasing when using HttpClient class to post to a web api.
URL NameTempTableCount-property-shows-number-of-active-temp-tables-increasing-when-using-HttpClient-class-to-post-to-a-web-api
Article Number000206656
EnvironmentProduct: OpenEdge
Version: 12.2
OS: Linux
Question/Problem Description

Progress.Database.TempTableInfo:TempTableCount shows number of active temp-tables increasing when using HttpClient class to post to a web API.

TempTableCount property in the Progress.Database.TempTableInfo class shows number of active temp-tables increasing in the same session when using HttpClient class to post to a web API.

Is TempTableCount an accurate property for seeing the number of active temp-tables in one ABL session?


Steps to Reproduce
Clarifying Information
- Using HttpClient class to post JSON payloads in a batch program.  Concerns that max temp-table limit will be reached for a session. 
- Delete Object statements are in place in the code.  
Error Message
Defect NumberDefect OCTA-41331
Enhancement Number
When a class has a temp-table and multiple buffers for that temp-table, and the object gets reused, it causes the Progress.Database.TempTableInfo:TempTableCount to get out of sync, and also causes the temp-table logging at level 3 or higher to log multiple entries for reusing that temp-table (as many instances as there are buffers defined for that temp-table).  This issue does not represent a leak in the application code or the AVM.  There are no temp-tables leaking and there are not as many temp-tables in scope as the TempTableCount would indicate.  Only the reporting is affected.   Although the temp-table logging will show many entries for 'Reuse' of the same temp-table in a sequence before it says it was cached, the logging does correctly show how many temp-tables were created. 
Until the fix is available, use the workaround below.
Start the session with -reusableObjects 0 as a way to workaround this issue. 
Last Modified Date11/23/2021 10:03 PM
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.