I am still doing stuff on code 
currently adding a utility to kill errant MySQL connections
.NET appears to have a bug with how pooling MySQL connections are handled and leaves too many sleeping connections without closing them, can cause problems in a hosted environment.
currently adding a utility to kill errant MySQL connections
.NET appears to have a bug with how pooling MySQL connections are handled and leaves too many sleeping connections without closing them, can cause problems in a hosted environment.
Postet den
thanks for update. I feel your pain I'm getting hacked off with services being stopped but showing as running.
Postet den
Originally posted by HuwR
I am still doing stuff on code
currently adding a utility to kill errant MySQL connections
.NET appears to have a bug with how pooling MySQL connections are handled and leaves too many sleeping connections without closing them, can cause problems in a hosted environment.
I have added some code to autokill sleeping connections when using MySQL. Torborg's test site has been updated so I can keep an eye on it (it was suffering from too many open connections and dying due to exceeding its max limit)
Postet den
Postet den
You'll be happy to know that I have no clue what this means but good luck fixing it anyway
