Hi, today I noticed the error mentioned in the title.
Us and our client have been using a custom CMS and of course the ticket response was to properly close my connections.
I just went through all the instances of connecting to database in our code and found them all being closed and disposed of.
Connections stay in the “Processes” list of phpmyadmin for several minutes in the state of “Sleep”. Should that state not be “open” if they were not being closed properly?
is it using a mysql pconnect or mysql connect? a pconnect will stay zombied
i dont know what those two functions translate to in asp.net, but this cms is working ok on other sites which are hosted elswhere
i added pooling=false into connection string and the problem went away.
don’t know yet, what this will do to performance though…
That means you were indeed using persistant connections that is not a way to go in shared hosting. Also FYI, sleep mode means that connection is still open.
That actually makes sense if I think about it.
So what you are saying is that I don’t close all my database connections properly?