Too many connection

Yes your correct thats exactly what it says.

Solution obviously being...

#1: Hold a connection open and process all sql queries through it.
#2: Close your connections when you're done with them.

Problem solved!

Quote:

Originally Posted by pro4never Solution obviously being... #1: Hold a connection open and process all sql queries through it. #2: Close your connections when you're done with them. Problem solved!

thanks for your help but can u explain more please i'm noop:handsdown: i'm use old mysql win (binary 95 mysql)

I swear you should give like 80% of your donations to the community here, without us your server wouldnt be online >_>.

I mean come on, atleast try and fix it yourself, go research that error.

Didn't Fang give people a killconnection system ?

instead of using things like "kill all connection system"...
why not just use EO mysql functions??? its easy to extract and you can build your own sql wrapper.... its fast and better.... since you just need to read a little...
Btw... its just an idea ^^

Quote:

Originally Posted by 12tails instead of using things like "kill all connection system"... why not just use EO mysql functions??? its easy to extract and you can build your own sql wrapper.... its fast and better.... since you just need to read a little... Btw... its just an idea ^^

give me link please of that mysql

Quote:

Originally Posted by magnon give me link please of that mysql

Eudemons source code, find it.

Solution... close and dispose of ALL connections after you're done using them or better yet, create a destructor method in the MySql read and write classes. Run the kill connections function I wrote and execute it on a thread within a while loop. Loop it every 5 minutes or so.

Basically what Fang said. Sure, if you close all the connections you SHOULD be okay, but that's not always the case. You really should prune the ones that didn't get closed every [insert interval here]. Just make sure you're not killing any active connections in the process of doing so. Also, the real problem you're having is that you didn't set your MySQL Daemon's max_connections higher than the standard amount for a home computer, which you should have done during the setup process..

Quote:

Originally Posted by Zeroxelli Basically what Fang said. Sure, if you close all the connections you SHOULD be okay, but that's not always the case. You really should prune the ones that didn't get closed every [insert interval here]. Just make sure you're not killing any active connections in the process of doing so. Also, the real problem you're having is that you didn't set your MySQL Daemon's max_connections higher than the standard amount for a home computer, which you should have done during the setup process..

My function kill connections that are sleeping. You should close all connections after using them or you'll run into problems. My function doesn't make up for bad programing techniques.

Quote:

Originally Posted by Fаng My function kill connections that are sleeping. You should close all connections after using them or you'll run into problems. My function doesn't make up for bad programing techniques.

Well then that's good, I hadn't looked at it. And nothing really does clean up after bad programming.

Solution:
>Connect
>Execute
>Close Connection

DON'T KEEP CONNECTIONS OPEN!!!!!!!!!!!!

Fuck MySQL anyways.

Quote:

Originally Posted by I don't have a username Solution: >Connect >Execute >Close Connection DON'T KEEP CONNECTIONS OPEN!!!!!!!!!!!! Fuck MySQL anyways.

MsSql has the same problem with sleeping connections (I believe). I haven't gotten far enough to implement my function yet on my server. I'll do that tomorrow (maybe) and double check.