Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m currently working on a legacy ASP.NET 2.0 web application using a MySQL 5 database.
At user login a list of all slept processes are retrieved and killed off.
Why is this task performed in the application (connection leak?)? I would have assumed connection pooling would have taken care of this, but I’m not familiar enough with MySQL to say for sure.
A week later after a more thorough review it turns out a single connection to the database was not closing correctly and a previous developer selected the nuclear option to fix it.