#28 Exception on invalid communication on Console port

[Danny Faught]

I was having trouble connecting to the Console, so I
tried to use telnet to verify whether I could connect.
This exception was the result.

1) Run the Console
2) Telnet to the console port and press Enter
3) The Console pops up an error dialog that says
"Queued exception". Terminal output from the Console is:

$ (Nested exception) java.io.StreamCorruptedException:
invalid stream header
at
java.io.ObjectInputStream.readStreamHeader(Unknown Source)
at java.io.ObjectInputStream.<init>(Unknown Source)
at
net.grinder.communication.SocketSet$HandleImplementation.pollForMessage(SocketSet.java:193)
at
net.grinder.communication.UnicastReceiver$ListenThread.run(UnicastReceiver.java:177)
<truncated>
net.grinder.communication.CommunicationException:
Queued exception
at
net.grinder.communication.MessageQueue.dequeue(MessageQueue.java:123)
at
net.grinder.communication.AbstractReceiver.waitForMessage(AbstractReceiver.java:70)
at
net.grinder.console.ConsoleCommunication.waitForMessage(ConsoleCommunication.java:175)
at
net.grinder.console.Console.run(Console.java:137)
at net.grinder.Console.main(Console.java:50)

While some sort of error message is probably warranted,
this is a cryptic error that isn't likely to help the
user understand what caused the problem.

[Philip Aston]

Logged In: YES
user_id=2117

I don't consider this particularly unreasonable behaviour.
Users that attempt to telnet to an application port should
know what they're doing; they are usually using telnet to
check whether an application is listening on the port (any
response is a good one) and they shouldn't expect the
application to handle the request.

[Danny Faught]

Logged In: YES
user_id=576825

I filed this issue before I realized that exceptions were
used as the primary method of error notification to the user.