MC-993Console Stack Trace :: Invalid argument
After the server has had about 24 hours of uptime, the console started spamming the following stack trace. Restart makes it subside.
java.net.SocketException: Invalid argument
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.net.SocketInputStream.read(SocketInputStream.java:203)
at java.io.FilterInputStream.read(FilterInputStream.java:83)
at dx.a(SourceFile:177)
at bx.i(SourceFile:248)
at bx.c(SourceFile:23)
at by.run(SourceFile:101)
Environment
- Operating System: Mac OS X (x86_64) version 10.8.1
- Java Version: 1.7.0_07, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 918602576 bytes (876 MB) / 3221225472 bytes (3072 MB) up to 3221225472 bytes (3072 MB)
- JVM Flags: 5 total; -Xmx3G -Xms3G -Xloggc:server_gc.log -XX:+UseG1GC -XX:+DisableExplicitGC
- AABB Pool Size: 34241 (1917496 bytes; 1 MB) allocated, 0 (0 bytes; 0 MB) used
Created Issue:
Console Stack Trace :: Invalid argument
After the server has had about 24 hours of uptime, the console started spamming the following stack trace. Restart makes it subside.
java.net.SocketException: Invalid argument at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:150) at java.net.SocketInputStream.read(SocketInputStream.java:121) at java.net.SocketInputStream.read(SocketInputStream.java:203) at java.io.FilterInputStream.read(FilterInputStream.java:83) at dx.a(SourceFile:177) at bx.i(SourceFile:248) at bx.c(SourceFile:23) at by.run(SourceFile:101)Environment
- Operating System: Mac OS X (x86_64) version 10.8.1
- Java Version: 1.7.0_07, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 918602576 bytes (876 MB) / 3221225472 bytes (3072 MB) up to 3221225472 bytes (3072 MB)
- JVM Flags: 5 total; -Xmx3G -Xms3G -Xloggc:server_gc.log -XX:+UseG1GC -XX:+DisableExplicitGC
- AABB Pool Size: 34241 (1917496 bytes; 1 MB) allocated, 0 (0 bytes; 0 MB) used
- Unresolved
- Open
- Public
- Unconfirmed
- searver stacktrace
- 1.4.2
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I have not seen this particular behavior in later versions.