• Hello Guest! Did you know that ProjectKorra has an official Discord server? A lot of discussion about the official server, development process, and community discussion happens over there. Feel free to join now by clicking the link below.

    Join the Discord Server

What does this error mean?

ServerElementals

Verified Member
Code:
23.12 20:39:37 [Multicraft] stretco ran command Message of the Day
23.12 20:39:37 [Server] WARN com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.
23.12 20:39:37 [Server] WARN at sun.reflect.GeneratedConstructorAccessor123.newInstance(Unknown Source)
23.12 20:39:37 [Server] WARN at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
23.12 20:39:37 [Server] WARN at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.Util.getInstance(Util.java:387)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:917)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:896)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:885)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:860)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.ConnectionImpl.throwConnectionClosedException(ConnectionImpl.java:1246)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.ConnectionImpl.checkClosed(ConnectionImpl.java:1241)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.ConnectionImpl.prepareStatement(ConnectionImpl.java:4102)
23.12 20:39:37 [Server] WARN at com.mysql.jdbc.ConnectionImpl.prepareStatement(ConnectionImpl.java:4071)
23.12 20:39:37 [Server] WARN at com.projectkorra.projectkorra.storage.Database.readQuery(Database.java:119)
23.12 20:39:37 [Server] WARN at com.projectkorra.projectkorra.GeneralMethods.createBendingPlayerAsynchronously(GeneralMethods.java:304)
23.12 20:39:37 [Server] WARN at com.projectkorra.projectkorra.GeneralMethods.access$000(GeneralMethods.java:143)
23.12 20:39:37 [Server] WARN at com.projectkorra.projectkorra.GeneralMethods$1.run(GeneralMethods.java:297)
23.12 20:39:37 [Server] WARN at org.bukkit.craftbukkit.v1_11_R1.scheduler.CraftTask.run(CraftTask.java:58)
23.12 20:39:37 [Server] WARN at org.bukkit.craftbukkit.v1_11_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:355)
23.12 20:39:37 [Server] WARN at net.minecraft.server.v1_11_R1.MinecraftServer.D(MinecraftServer.java:811)
23.12 20:39:37 [Server] WARN at net.minecraft.server.v1_11_R1.DedicatedServer.D(DedicatedServer.java:403)
23.12 20:39:37 [Server] WARN at net.minecraft.server.v1_11_R1.MinecraftServer.C(MinecraftServer.java:749)
23.12 20:39:37 [Server] WARN at net.minecraft.server.v1_11_R1.MinecraftServer.run(MinecraftServer.java:648)
23.12 20:39:37 [Server] WARN at java.lang.Thread.run(Thread.java:745)
23.12 20:39:37 [Server] WARN Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 248,194,055 milliseconds ago.  The last packet sent successfully to the server was 248,194,080 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
23.12 20:39:37 [Server] WARN at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 

xNuminousx

Verified Member
Code:
23.12 20:39:37 [Server] WARN Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 248,194,055 milliseconds ago.  The last packet sent successfully to the server was 248,194,080 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
Did you read that part?
 
Top