Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Useless messages in the console #63

Open
Blayung opened this issue Jan 19, 2024 · 1 comment
Open

Useless messages in the console #63

Blayung opened this issue Jan 19, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@Blayung
Copy link
Contributor

Blayung commented Jan 19, 2024

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)
@KoboDev
Copy link
Contributor

KoboDev commented Feb 15, 2024

This is simillar to #59
And yes its utterly annoying.

@KoboDev KoboDev added the duplicate This issue or pull request already exists label Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants