MySql Error. Buffer Maxing Out?

After I recoded my mysql system, I have been getting a weird ass mysql error after around 6-7 hours typically. After I get the error my mysql fails (wont let me reconnect) and I have to restart my dedi for the mysql to actually work again.

These are the errors:
I dont really need a step by step explanation, just need to know what can cause this error so i can fix it. I searched google, but it actually failed me for once. Anyone have any ideas on why the buffer is maxing?

FYI: The mysql system creates a new connection every query, and closes it right after. Figured this may be causing some of the problem, but I watched the mysql monitor and it stays below 30 connections.

ConquerSx explains it all.

Quote:

Originally Posted by stealarcher After I recoded my mysql system, I have been getting a weird ass mysql error after around 6-7 hours typically. After I get the error my mysql fails (wont let me reconnect) and I have to restart my dedi for the mysql to actually work again. These are the errors: Code: MySql.Data.MySqlClient.MySqlException: Unable to connect to any of the specified MySQL hosts. ---> System.Exception: Exception of type 'System.Exception' was thrown. at MySql.Data.MySqlClient.NativeDriver.Open() --- End of inner exception stack trace --- at MySql.Data.MySqlClient.NativeDriver.Open() at MySql.Data.MySqlClient.MySqlPool.CreateNewPooledConnection() at MySql.Data.MySqlClient.MySqlPool.GetPooledConnection() at MySql.Data.MySqlClient.MySqlPool.GetConnection() at MySql.Data.MySqlClient.MySqlConnection.Open() at ConquerSx.Database.MySqlReader.TryFill(MySqlCommand command) in C:\Users\Chris\Desktop\source\source\Database\MySqlReader.cs:line 72 at ConquerSx.Database.MySqlReader..ctor(MySqlCommand command) in C:\Users\Chris\Desktop\source\source\Database\MySqlReader.cs:line 19 at ConquerSx.Database.Core.Loadconfig() in C:\Users\Chris\Desktop\source\source\Database\Core.cs:line 11 at ConquerSx.Program.Main(String[] args) in C:\Users\Chris\Desktop\source\source\Program.cs:line 85 ServerIP: 64.74.97.228 ServerIP: 64.74.97.228 System.NullReferenceException: Object reference not set to an instance of an object. at ConquerSx.PacketHandling.PickItemUp.Handle(GameClient GC, Byte[] Data) in C:\Users\Chris\Desktop\source\source\PacketHandling\PickItemUp.cs:line 15 at ConquerSx.PacketHandler.Handle(GameClient GC, Byte[] PData) in C:\Users\Chris\Desktop\source\source\PacketHandler.cs:line 651 System.NullReferenceException: Object reference not set to an instance of an object. at ConquerSx.Database.MySqlReader.Read() in C:\Users\Chris\Desktop\source\source\Database\MySqlReader.cs:line 94 at ConquerSx.Database.items.NewItem(Item Item, UInt32 PlayerEntityID) in C:\Users\Chris\Desktop\source\source\Database\items.cs:line 71 Saved. I dont really need a step by step explanation, just need to know what can cause this error so i can fix it. I searched google, but it actually failed me for once. Anyone have any ideas on why the buffer is maxing? FYI: The mysql system creates a new connection every query, and closes it right after. Figured this may be causing some of the problem, but I watched the mysql monitor and it stays below 30 connections.

Just an idea and not really helping with the error, but why don't you have 1 constant open connection to MySql and then send everything through that instead of opening up new connections all the time... Less Stress = Less Lag = Better Server

Because in all honesty you will run into alot of problems when you have more than 10 people trying to connect...

You have to think.. each query = 1 MySql connection... If 50 people log in and then do something that needs a save, thats 50+ MySql connections opening and then opening again to save something else...

Just seems a bit errr "Stupid" to have your MySql like that < Not meaning to flame :)


As for the Buffer Maxing out I have never seen that error before so unfortunatly can't help you out buddy

Well, ive always heard of mysql timing out crashing etc, and this way i figured it couldnt do that rofl.

Quote:

Originally Posted by stealarcher Well, ive always heard of mysql timing out crashing etc, and this way i figured it couldnt do that rofl.

Yeah but this way you are more likely to flood the MySql connections and then max out the pool and crash the server that way

hmm, may be right, ill try it out with a solid connection and see how it goes then.

Why don't you just use Immunes or Impulse MySQL?

u cant download Impulse's source anymore the download was removed

Actually you can download the source, if you go down the first page on the thread then you will see alot of download links.

Quote:

Originally Posted by coreymills u cant download Impulse's source anymore the download was removed

Also he posted the way he handle MySQL if you look in a thread here on first page.

I believe impulses source creates a new connection each query as well. He uses using (connection) which disposes it and creates it, and opens it every time. Forgive me if im wrong, but im pretty sure it does.

Quote:

Originally Posted by stealarcher I believe impulses source creates a new connection each query as well. He uses using (connection) which disposes it and creates it, and opens it every time. Forgive me if im wrong, but im pretty sure it does.

No Impulse uses a "solid" connection

It open up when the source does and stays open and sends everything through that connection...

Hmm, i looked through his source. it calls a void called SelectConnection, which gets the mysql connection. In the mysql connection its set to return new. Isnt that creating a "new" connection every time the SelectConnection is called?

Yes it is, and theres nothing really wrong with creating a new connection everytime you need one, the majority of websites work in this fashion.

@Korvacs
Yeah, thats what I was thinking. I didnt think there was anything wrong with it, and figured it would prevent the connection from timing out etc that way. But sense this error isnt caused by too many connections obviously. Any idea what causes it?