[MC-993] Console Stack Trace :: Invalid argument Created: 28/Oct/12  Updated: 10/May/17  Resolved: 27/Nov/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: Minecraft 1.4.5

Type: Bug
Reporter: Anthony Martin Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: server, stacktrace
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

Confirmation Status: Unconfirmed

 Description   

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)


 Comments   
Comment by Anthony Martin [ 26/Nov/12 ]

I have not seen this particular behavior in later versions.

Comment by Tails [ 26/Nov/12 ]

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.

Generated at Sun Jan 12 11:52:56 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.