search

games647 / FastLogin

Checks if a minecraft player has a valid paid account. If so, they can skip offline authentication automatically. (premium auto login)
https://www.spigotmc.org/resources/fastlogin.14153
MIT License
503 stars 121 forks source link

Connection is not available, request timed out #1002

Closed david160596 closed 1 year ago

david160596 commented 1 year ago

What happened?

Using Waterfall version #514 or higher, this database connection error occurs and does not allow users to connect to the server: https://hastebin.com/share/oterigifec.ruby

However, reverting to a lower version of Waterfall such as #510 works perfectly and connects without any problems.

What did you expect?

I was hoping it would be able to connect without any problems with the latest version of Minecraft 1.19.4.

Steps to reproduce

Try to connect to the server with more users, at first it will be fine, but after a couple of attempts to connect and reconnect you will get this connection failure in the Proxy console and no user will be able to enter the server.

Plugin list

FastLogin, Floodgate, Geyser-BungeeCord, SkinsRestorer.

Configuration file

In the config we are using MySql with Driver in the config 'com.mysql.cj.jdbc.Driver'.

Server log

Plugin loads correctly without errors: https://hastebin.com/share/eponuqecut.less

Plugin version

Build #1214

Platform

Waterfall

Relevance

games647 commented 1 year ago

This means that the MySQL didn't answered the requests or the connection management got stalled. It might be related to https://github.com/brettwooldridge/HikariCP/commit/e4bbce715235d52751469f9cf861a4c5b6e2450f . However, this would only occur if there was an earlier error. Could you search your log for error code 1105 or HY000?

david160596 commented 1 year ago

There is no error prior to the one I sent you, neither 1105 nor HY000 or any other.

Thank you for trying to help fix it.

games647 commented 1 year ago

I got another report about this issue. I'm merging these two tickets to #1022. It really appears to be related to the driver. I uploaded there some test versions with specific optimizations disabled, they could trigger the bug. Maybe I can report it upstream.

EDIT: Thank you for the version report. It was helpful to pinpoint the source origin.