Fix to Begin Nested Exception Error

keroh93 · Jul 29, 2009

Code:

[COLOR="Red"]ONLINE: 150+ Hours[/COLOR]

Has anyone ever gotten this error inside their launcher.bat?

Code:

Begin Nested Exception
Communication Link Failure

blah blah blah blah

Did this error come up when you were about to login, but then it said your ID is not Registered?
Or even when you got past that login screen, was your character missing?
If this error pops up, it means that the server and the database has both disconnect from each other and will not transfer data over.

Reason:

When about only 0-3 players are on, the server isn't sending much data over to the database (MySQL)
When MySQL and the Server thinks there is a wait time for a certain amount of time, the database will then go idle. During that idle time, if there is still no HUGE data going through from the server to the database, it usually takes 3-8 hours for the database to actually shut down completely, and therefore, you will start getting the Begin Nested Expception error. You will not be able to login properly, or even login to your character properly. So basically, after a certain amount of time, the server and the database will close connection to each other! I am currently testing this out, my server used to shut down at around 15+ hours and never got past 25 hours. Currently I only have about 0-6 players on, at most is about 0-10 players.
I am currently in need for some testers to test this out for me. I have had my server up and running for more than 35+ hours.

In your DB.Properties it should look something like this (hopefully

Code:

driver=com.mysql.jdbc.Driver
url=jdbc:mysql://127.0.0.1:3306/odinms
user = root
password = root

At the end of odinms (or your database name) put the following code

Code:

?autoReconnect=true

So now it should look like this

Code:

driver=com.mysql.jdbc.Driver
url=jdbc:mysql://127.0.0.1:3306/odinms?autoReconnect=true
user = root
password = root

Of course, do this when the server is down. Save. And start up your server again!

Reason:
The reason why I'm telling you to put ?autoReconnect=true in the DB.Properties, is because, after the server loses connection with the database, it will reconnect to the database and you will not get any of those errors!

I am still testing this, I am currently going to test this out for about 3-5 days straight without shutting down my own server.
If this method fails for me, I will tell you all, and I will post up another method I have in mind.

Please use this method above (?autoReconnect=true) and tell me if it is working for you!

Credits:
kyrokeroh - Keroh93