[Crash] FoException: Report: Connection was never established, did you call connect() on org.mineacademy.chatcontrol.model.db.Da

[kangobot]

Auto-reported crash

Key	Value
Plugin	ChatControl 12.2.1
Server	Paper 26.1.2.build.63-stable
Players Online	1
BBB Nonce	a94cb31f53f44fec16892da7fc261835
db_type	local
db_player_type	uuid
proxy_enabled	false

Context

Connection was never established, did you call connect() on org.mineacademy.chatcontrol.model.db.Database@7ae87627?

Stack Trace

FoException: Report: Connection was never established, did you call connect() on org.mineacademy.chatcontrol.model.db.Database@7ae87627?
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.lib.ValidCore.checkBoolean(ValidCore.java:72)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.lib.database.SimpleDatabase.ensureConnected(SimpleDatabase.java:486)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.lib.database.SimpleDatabase.borrowConnection(SimpleDatabase.java:1451)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.lib.database.SimpleDatabase.prepareStatement(SimpleDatabase.java:1227)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.lib.database.SimpleDatabase.select(SimpleDatabase.java:1026)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.model.db.Database.getPlayerCacheWhereStrict(Database.java:595)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.model.db.Database.loadOrCreateCache(Database.java:579)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.model.db.Database.lambda$loadAndStoreCache$0(Database.java:512)
	at ChatControl-12.2.1.jar//org.mineacademy.chatcontrol.lib.CommonCore.lambda$wrapRunnableInExceptionCatcher$0(CommonCore.java:1703)
	at org.bukkit.craftbukkit.scheduler.CraftTask.run(CraftTask.java:78)
	at org.bukkit.craftbukkit.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57)
	at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
	at java.base/java.lang.Thread.run(Thread.java:1474)

[kangarko]

Root cause found: reload tore the database pool down before rebuilding it, so any semantic error during settings re-init (bad database Type, invalid time string and similar) left the plugin enabled with no pool, and every join then fired this report. Player cache loads also had no connection gate unlike their sibling paths.

Fixed in the next release: reload now swaps the pool atomically so a failed reload keeps the old connection serving, player cache loads wait for the connection with a bounded retry instead of throwing, and a server whose tables cannot be created disables the plugin instead of running half-alive.

[kangarko]

Fixed in 12.2.2. The database stays connected across /chc reload, and player data that was still loading is retried instead of lost.