SQLite completely crashing server
rmichela opened this issue ยท 4 comments
I am getting serious problems with SQLite locking up the entire server. I can only solve the problem by killing the server's process and restarting.
23:44:14 [INFO] [PreciousStones] Disabling PreciousStones v9.5.2
23:44:23 [WARNING] [Server] The main thread failed to respond after 10 seconds
23:44:23 [WARNING] [Server] Probable Plugin cause: 'PreciousStones'
23:44:23 [WARNING] [Server] What follows is the stack trace of the main thread
23:44:23 [WARNING] [Server] at org.sqlite.NativeDB.finalize(Native Method)
23:44:23 [WARNING] [Server] at org.sqlite.DB.close(DB.java:96)
23:44:23 [WARNING] [Server] at org.sqlite.Conn.close(Conn.java:250)
23:44:23 [WARNING] [Server] at net.sacredlabyrinth.Phaed.PreciousStones.storage.SQLiteCore.close(SQLiteCore.java:104)
23:44:23 [WARNING] [Server] at net.sacredlabyrinth.Phaed.PreciousStones.managers.StorageManager.closeConnection(StorageManager.java:258)
23:44:23 [WARNING] [Server] at net.sacredlabyrinth.Phaed.PreciousStones.PreciousStones.onDisable(PreciousStones.java:233)
23:44:23 [WARNING] [Server] at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:219)
23:44:23 [WARNING] [Server] at org.bukkit.plugin.java.JavaPluginLoader.disablePlugin(JavaPluginLoader.java:400)
23:44:23 [WARNING] [Server] at org.bukkit.plugin.SimplePluginManager.disablePlugin(SimplePluginManager.java:400)
23:44:23 [WARNING] [Server] at org.bukkit.plugin.SimplePluginManager.disablePlugins(SimplePluginManager.java:393)
23:44:23 [WARNING] [Server] at org.bukkit.craftbukkit.CraftServer.disablePlugins(CraftServer.java:265)
23:44:23 [WARNING] [Server] at net.minecraft.server.MinecraftServer.stop(MinecraftServer.java:350)
23:44:23 [WARNING] [Server] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:457)
23:44:23 [WARNING] [Server] at net.minecraft.server.ThreadServerApplication.run(SourceFile:856)
The error happened when I issued a /stop command. Prior logs were the standard shutdown process. The above is the stack trace when the server crashed. Switching the MySql fixed this problem.