You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, when anybody disconnects from the server, a java.net.SocketException stacktrace is printed in the console with the severe logger. You could maybe get rid of it in that fork?
20:17:56 [INFO] _Blay_ lost connection: disconnect.quitting
20:17:56 [SEVERE] java.net.SocketException: Socket closed
20:17:56 [SEVERE] at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:118)
20:17:56 [SEVERE] at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
20:17:56 [SEVERE] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
20:17:56 [SEVERE] at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
20:17:56 [SEVERE] at java.io.DataOutputStream.flush(DataOutputStream.java:123)
20:17:56 [SEVERE] at net.minecraft.server.NetworkWriterThread.run(NetworkWriterThread.java:43)
The text was updated successfully, but these errors were encountered:
Basically, when anybody disconnects from the server, a java.net.SocketException stacktrace is printed in the console with the severe logger. You could maybe get rid of it in that fork?
The text was updated successfully, but these errors were encountered: