"max pool size was reached" problem

[thimsing]

We migrated our web server from a single processor, 1 GB RAM to a dual-processor blade server with 2 GB RAM and we hit this problem. We did not make any changes to the pool size i.e. using the default settings.

We had encountered this problem occasionally (1-2 times a month) much earlier in the previous server and we tidied up our application to explicitly close the connections and the problem went away.

When we moved to the new servers (incl the database and the application servers), this problem occurs everyday from the 4th day onwards (since the move) with increasing frequency. Each time we did the IISReset. At the SQLServer, we noticed about 40 connections at the time of the problem.

As a temporary measure, we increased the max pool size to 400 and we discovered that the no of connections could hit the 400 mark. What we could not understand is why this did not happen in the old servers if there was still a problem with our application.

As the number of users are limited by our RAS, there is no significant increase in the usage especially in the span of 1-2 weeks.

[Xoc]

<bump> Anyone have any ideas on this?