Feedback
Did this article resolve your question/issue?

   

Article

OpenAccess memory leak with example1 IP and Thread/Connection model

Information

 
TitleOpenAccess memory leak with example1 IP and Thread/Connection model
URL NameOpenAccess-memory-leak-with-example1-IP-and-Thread-Connection-model
Article Number000115557
EnvironmentProduct: OpenAcess SDK server
Version: 8.1.0.0088
OS: Solaris SPARC 32-bit, 64-bit
Database: N/A
Application odbcisql, example
Question/Problem Description
OpenAccess oasoa process memory leak with example1 IP using ServiceConnectionModel=Thread/Connection
Steps to ReproduceSteps to reproduce issue:
1) Build the example1 sample IP and start the OpenAccess server that is using Thread/Connection model
2) Obtain the C service oasoa process id.
3) Monitor the oasoa process memory using prstat -p <oasoa pid>
4) Connect using the OpenAccess ODBC client using example program and execute the below query multiple times.
select * from cur_value;

Observed Results:
The oasoa process memory increases and does not reduce even after the ODBC client application disconnects.
Clarifying Information
Error Message
Defect NumberDefect OASL-293
Enhancement Number
Cause
The exact cause is not known at this time.
Resolution
Until a resolution is available, use the workaround listed below.
Workaround
Stop and restart the OpenAccess C service.
Notes
Last Modified Date6/21/2019 12:38 PM
Files
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.