Link to home
Start Free TrialLog in
Avatar of toanstt
toanstt

asked on

Memory could not be allocated

Please help me.
I have a critical problem. I wrote a web service that use ASP.NET.
In my application, I use a thread pool for processing and Oracle connection pool to connection to Oracle Server, test on Window 2003 Server. After that, we use a program connect to the web service every 100ms. The program runs for long time, maybe 6 hours, and after that I got the error in my log files:
"Memory could not be allocated" and some time I got the log: "Connection request timed out".

We see that the performance counter, the private bytes memory is greater than the virtual bytes.
I don't know this bug that occurs by .NET or IIS server.
Please help me to fix this bug.

Thanks
ASKER CERTIFIED SOLUTION
Avatar of naveenkohli
naveenkohli

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of toanstt
toanstt

ASKER

Thanks for reply to me.

1. I found some wrong code about the connection. If the connection get timed out, the connection doese not close.

2. In my server, we do not use the load balanced web server. I also think that connect to a web service every 100ms is not a very practical, after that I change every 30 seconds to connect to my server.
The problem still happend. In my test server, we have 2GB memory. When the bug occurs, the memory still does not reach 2GB memory.

Do you think that this is a bug of Framework 1.1.

Thanks
I will suggest to use a memory profiler to see why memory consumption is increasing and who is holding on to it.
Avatar of toanstt

ASKER

Could you please tell me the name of the tool?