August 17, 2006 at 6:18 pm
We are begining to get "Maximum number of connections reached" errors... and sql server (2000) is refusing further connections.
We are definately not anywhere near 32,767..
What else would be generating this error?
Ilmar
August 18, 2006 at 4:55 am
Your application might not be closing the connection properly. run sp_who2 'active' or from Enterprise manager, Managment/Current Activity and click on Process Info which shows you all the connections to the server
chears
August 18, 2006 at 7:04 am
I get this problem every now and then. I've pretty much narrowed it down to java apps (especially if the connections are managed by Tomcat) not closing connections properly.
The only ways to fix it I have found is to manually kill the processes, or occasionally bounce the Tomcat service late at night.
Niether solution is that good, but it happens infrequently enough that I haven't put much time into finding anything better.
The Redneck DBA
August 18, 2006 at 9:48 am
I have a similar issue, is there nothing to compare to mysql's wait_timeout or interactive_timeout ?
August 18, 2006 at 6:00 pm
Thanks folks.. I'm begining to find places in the application framework that are leaving connections open... the hunt is on!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply