[Help] Max Pooled Connections??? :S

Hey guys, I keep getting an error after about 15 minutes of my server being online...

[Only registered and activated users can see links. Click Here To Register...]

When a character is saved it opens a new connection and then closes it after, it does this all the time it connects to MySql.

e.g
Connection Open - Read/Write - Connection Close

Have I done something seriously wrong? Or is it just my MySql being funny?

Many thanks to anyone who can help

Are you using AppServer? If you are, uninstall it and install MySQL 5.5. Then on set up, change the concurrent connections to 2000+. That's all I can think of. I've never seen this error before =[

seems like ur mysql connection is really bad.
anyways fang appserv should not be the problem as is only 1 connection.
It have to be somewhere in his mysql code ><

I got no idea thought >.<

Not directly related to the question but you may wanna look into the sql wrapper made by impulse. It's DELICIOUS.

I forget all the technical details behind it but basically it kicks serious ass and makes methods far simpler to write.

I THINK it worked along the lines of establishing a single connection to sql which then handles all requests and inputs between the server and sql. That way you don't have to worry about opening/closing so many connections or any issues with threading as it's all handled through the same connection.

Quote:

Originally Posted by pro4never Not directly related to the question but you may wanna look into the sql wrapper made by immune. It's DELICIOUS. I forget all the technical details behind it but basically it kicks serious ass and makes methods far simpler to write. I THINK it worked along the lines of establishing a single connection to sql which then handles all requests and inputs between the server and sql. That way you don't have to worry about opening/closing so many connections or any issues with threading as it's all handled through the same connection.

>.> immune's?

Thanks for the ideas guys I am probably gonna take pros idea and add immunes the Sql wrapper. If that doesnt work then I will try some other stuff.

Also with my appserv I know that is not the problem now because my Classic server is working fine with 60+ players.

Quote:

Originally Posted by .Beatz Thanks for the ideas guys I am probably gonna take pros idea and add immunes the Sql wrapper. If that doesnt work then I will try some other stuff. Also with my appserv I know that is not the problem now because my Classic server is working fine with 60+ players.

i think this sql was made by -impulse-
no immune

Quote:

Originally Posted by -impulse- >.> immune's?

Shit... so sorry, I always seem to mix up your names.. that + a while ago he was tving me a sql system he was working on.


But yes... your sql system is awesome, sorry for the mix up.

I would also check the MySQL Settings (i like to use MySQL Administrator) Double check if you use too much threads for MySQL coz that could cause your CPU to process much more Threads than needed and the connections or read/write could be delayed and run outta time - TimeOut

I have figured out the problem (I hope)... Keep Alive Interval was set to 240 and now I have disabled it and no more errors so far.

Quote:

Originally Posted by .Beatz When a character is saved it opens a new connection and then closes it after

Sounds like a terrible way to manage it all. Whoever thought of that... I have nothing to say. A better way would be to have your own persistent connection pool that you cycle through with each query.

Quote:

Originally Posted by bone-you Sounds like a terrible way to manage it all. Whoever thought of that... I have nothing to say. A better way would be to have your own persistent connection pool that you cycle through with each query.

I know it is a bad way to manage it at the moment but I am changing everything around I just needed to figure out this problem before I started changing stuff around.

Quote:

Originally Posted by .Beatz I know it is a bad way to manage it at the moment but I am changing everything around I just needed to figure out this problem before I started changing stuff around.

What I suggested would be the best method to do even though you could probably get away with doing just one connection and having a mysql queue.

sockets crash ?

Quote:

Originally Posted by †he Knight sockets crash ?

please quit.