+972 52-548-6969
Required: Debugging / Crash recovery assistance in NJ / NY
A client of mine has run into a production problem, and we need to dig into the application to understand what is going on. Unfortunately, I am not on site, so the level of help that I can contribute currently is not that great.
We are looking for someone that can come onboard and help us figure out what the exact problem is.
I don't have all the details about the production issue yet, but the symptom is very high connection count to the database, and the OS refusing connections with TIME_WAIT. We are pretty sure that there is a connection leak somewhere, but so far we have no been able to identify it.
The application in question compromise of classic ASP, ASP.Net and .Net Window Services talking to a Sql Server 2000 database.
My client is interested in someone who can come onsite and diagnose the issue. They are located in Fort Lee, NJ, near the GWB. Obviously we would like to get to the root of the issue ASAP. If you think that you can help, please contact me and I will put you in touch with my client.
And yes, this does seems like a scenario right out of Release It!
Comments
Oren,
There are two things we had to set on some of our higher utilized SQL servers that were refusing connections.
For WinsockListenBacklog you can find the registry key at http://support.microsoft.com/kb/154628/EN-US/. Please note that you will need to restart the SQL Server service for this setting to take effect.
For SynAttackProtect you can find the registry key at technet2.microsoft.com/.../...0242504d8ba1033.mspx. Please note that you will need to reboot the server for this setting to take effect.
Check those out and see if they are an easy tweak you can use to get out of the mud until you can more closely troubleshoot the issue.
Did you try to modify the connection string and set a higher value to MaxPoolSize...
Why can't you debug remotely?
Oren,
If you/anyone is able to solve this problem, please post the steps as to how it was fixed (if that is not a problem).
Your blog is widely read & I think it will help a lot of people.
Also, try posting this question on stackoverflow :)
Comment preview