Morningstar42
Glowing Redstone
- Joined
- Mar 29, 2012
This seems to maybe be a persistance of an earlier bug that is believed to have been fixed.
I'm on Spout 1368 (dunno if that matters for the bug) and it is disconnecting me if I type something into chat that is longer than ~110 characters. Different behavoirs happen depending on the length. The errors it throws are:
Internal exception: java.net.SocketException: Software caused connection abort:recv failed
(after submitting 130, 140 char chat msgs)
Internal exception: java.net.SocketException: Software caused connection abort: socket write error
(after submitting 120 char chat msg)
Disconnected by Server
(115 chars, 113 chars, 112 chars)
This one happens IMMEDIATELY and doesn't take 5-10 seconds to happen like the other errors
110 chars seems to work fine. This is in Local chat with no commands or switches submitted to the chat form. The failures and errors seem somewhat repeatable, in that I tested 120-140 and got the lag before dc'ing, tried 110-115 with their various results, then tried 140 again and still got lag before being dropped.
After submitting the chat message, some data seems to come through for a while afterwards (incoming chat and other events). It seems the chat data/packet is maybe found to be problematic between the client/server and eventually, but not immediately, kicks the user. There must be some mechanism that checks/relies on server/client confirmation of data transmitted, and eventually one of those times-out and drops the client connection from the server.
I'm on Spout 1368 (dunno if that matters for the bug) and it is disconnecting me if I type something into chat that is longer than ~110 characters. Different behavoirs happen depending on the length. The errors it throws are:
Internal exception: java.net.SocketException: Software caused connection abort:recv failed
(after submitting 130, 140 char chat msgs)
Internal exception: java.net.SocketException: Software caused connection abort: socket write error
(after submitting 120 char chat msg)
Disconnected by Server
(115 chars, 113 chars, 112 chars)
This one happens IMMEDIATELY and doesn't take 5-10 seconds to happen like the other errors
110 chars seems to work fine. This is in Local chat with no commands or switches submitted to the chat form. The failures and errors seem somewhat repeatable, in that I tested 120-140 and got the lag before dc'ing, tried 110-115 with their various results, then tried 140 again and still got lag before being dropped.
After submitting the chat message, some data seems to come through for a while afterwards (incoming chat and other events). It seems the chat data/packet is maybe found to be problematic between the client/server and eventually, but not immediately, kicks the user. There must be some mechanism that checks/relies on server/client confirmation of data transmitted, and eventually one of those times-out and drops the client connection from the server.
