Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Troubleshooting Timeout expired. All pooled connections were in use and max pool size was reached.

Reply
Thread Tools

Troubleshooting Timeout expired. All pooled connections were in use and max pool size was reached.

 
 
jobs
Guest
Posts: n/a
 
      11-09-2007
Re: Troubleshooting Timeout expired. All pooled connections were in
use and max pool size was reached.

New webservers. win2003. IIS6. asp.net 2.0/ sql server 2005 and Oracle
9i through a 64 bit Oracle client. Everything working fine until this.

I started getting these errors as the new website activity started to
heat up.

Timeout expired. The timeout period elapsed prior to obtaining a
connection from the pool. This may have occurred because all pooled
connections were in use and max pool size was reached.

After inspection of some of my methods I did see a few returning data
before disposing and closing.

I noticed these in the event log:

Event message: An unhandled exception has occurred.

The problem went away (at least for now) when I cycled the
applicationpool in IIS for the site.

A few dumb questions.

1. I did not see any significant activity on the webserver. How can I
troubleshoot this? Any way to see how many open connections? sessions
on the Web server? etc.

2. Looking at application pool setting, I thought I'd set down the
idle type before it recycles idle process to 5 minutes from 20
minutes. Good idea? what other settings might improve things?

Eventually I plan to loadbalance this webserver. It's currenty on
failover to an identical webserver.

Thank you for any help or information!

 
Reply With Quote
 
 
 
 
bruce barker
Guest
Posts: n/a
 
      11-10-2007
while a real high volume site (100+ concurrent users) might see and
require the pool sizes to be bumped up, usually its a coding error. the
database connections are not closed and returned to the pool. be sure
all code has a try/finally block that closes the connection or use the
using statement.

be sure connection are local, and never passed around, placed in session
or global variables. the routine that opens the connection, should close
before exiting. failure to close on error is a common defect.

-- bruce (sqlwork.com)


jobs wrote:
> Re: Troubleshooting Timeout expired. All pooled connections were in
> use and max pool size was reached.
>
> New webservers. win2003. IIS6. asp.net 2.0/ sql server 2005 and Oracle
> 9i through a 64 bit Oracle client. Everything working fine until this.
>
> I started getting these errors as the new website activity started to
> heat up.
>
> Timeout expired. The timeout period elapsed prior to obtaining a
> connection from the pool. This may have occurred because all pooled
> connections were in use and max pool size was reached.
>
> After inspection of some of my methods I did see a few returning data
> before disposing and closing.
>
> I noticed these in the event log:
>
> Event message: An unhandled exception has occurred.
>
> The problem went away (at least for now) when I cycled the
> applicationpool in IIS for the site.
>
> A few dumb questions.
>
> 1. I did not see any significant activity on the webserver. How can I
> troubleshoot this? Any way to see how many open connections? sessions
> on the Web server? etc.
>
> 2. Looking at application pool setting, I thought I'd set down the
> idle type before it recycles idle process to 5 minutes from 20
> minutes. Good idea? what other settings might improve things?
>
> Eventually I plan to loadbalance this webserver. It's currenty on
> failover to an identical webserver.
>
> Thank you for any help or information!
>

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Error when load testing web application: all pooled connections were in use or max pool size was reached Allan Ebdrup ASP .Net 1 05-14-2007 10:43 AM
Timeout Expired...max pool size was reached. =?Utf-8?B?Sm9u?= ASP .Net 0 10-03-2006 09:05 AM
Which allocator to use? For fixed-size, single-thread, pooled allocation? collection60@hotmail.com C++ 5 07-19-2006 10:13 PM
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. Guoqi Zheng ASP .Net 4 06-03-2004 06:39 PM
all pooled connections were in use dotNET Developer ASP .Net 2 02-24-2004 08:01 PM



Advertisments