MySQL V5.5.45&up + Dynmap 2.5 = SSL Errors about dynmapcore

[rouing]

I would switch to MairaDB over MySQL as there is major improvements and it is a drop in replacement. I will work on a pull request to add this option as I would like to see the option of having SSL on the connection anyways.

[nate2014jatc]

bumping this. The hardcoded option "?allowReconnect=true" causes the previous fix to cause more severe errors.

(previous fix being that you add "?useSSL=false" to your database name.)

[rouing]

@nate2014jatc Ayeyeye.

This needs to be ported to a config based option.

[aharabedian]

Is there any update on this issue? I am having the same issue with the hardcoded "?allowReconnect=true" flag.

[jwshields]

Add the ?useSSL=false after the ?allowReconnect=true

[aharabedian]

the ?allowReconnect=true flag is hard coded into DynMap, there is not a config option to add another flag. If you add the ?useSSL=false to the end of the database name, it causes an issue with the hard-coded flag and DynMap fails to connect to the database.

[nate2014jatc]

I can confirm. I'm still getting griped at to enable SSL and provide a truststore or globally disable SSL (not happening).

[aharabedian]

I created a fix and submitted a pull request. I have been using my build of v3.0 for the past day on my spigot server and it has been working fine, no SSL errors. If you build from my repo it will add a configuration option for flags. Hopefully it gets added as a feature.

[rouing]

I am the one who hardcoded the allow reconnect true and had the PR. This was to fix a DIFFERENT issue with latest versions of MYSQL/MARIADB dropping connections and not being allowed to connect. At this point, I am going to redo this to have a config to allow the use of a URI instead of user/pass/host/port by itself.