on 11-02-2004 2:05 PM
Hi Group,
I used SAP.NET Connector 2.0 to build a window service. It run as a server stub and recv request from client. it will do some searching from oracle and return the result as SAPTable as an out parameter in the RFC function.
I did a volume test by issuing 10,000 requests to that service and I observed from the Task Manager that the memory usage of that window service grow from 20mb to 800mb.
I am not sure it is a memory leak as the Garbage collection of .NET is non-deterministic. I suspect the "out" SAPTable hold up the memory.
Anybody here encounter the similar problem? Please advise.
Alex
Hello
Where is that memory leak documentet?
Regards,
Thomas Mouritsen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Please make sure that the file C:\<Windows>\system32\librfc32.dll is installed with the SAP .Connector 1.0.3 or 2.0 and has a version of 6206.6.1622.xxxx or greater. There was a RFC server related memory leak in earlier versions.
Can you exclude the possibility that the code that accesses Oracle DB leaks?
Regards,
Guangwei Li
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Li,
I did closely review my code and close, dispose every objects whenever possible. However, as i have said, since this function need to return a big SAPTable thr an "out" parameter, i cannot free those related variable within the scope of my function. If so, the SAP Client will recv nothing.
Any idea?
Alex
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.