Connection Pools maxed out?

.net, sql 2000

[mattglet]

every so often, this new site i developed comes up with this error:

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.

i know what the error means, but i can't figure out what's causing it. i just now have hard coded the connection pool size in my web.config file to 999 connections, but i imagine this will only lengthen the time until it happens again. i have multiple .NET sites on this server, but there is only one site that's having this database issue. i know what most people will say... "you need to close your connections, etc etc". i honestly can say that i'm 99% sure my connections are all closed. is there anything else i should be looking for? thanks for your quick responses.

if you would like to see the site, or need more details, sticky me.

-Matt

[duckhunter]

If you are not explicitly Closing your connection objects AND setting them to Nothing, .NET doesn't always release the garbage collection as you had hoped and you will end up with orphaned connections. Always set ALL objects to Nothing using .NET or you will run into issues

[mattglet]

ah, setting them to nothing... that's something i probably need to do. thanks duckhunter.

-Matt