Java Telnet client crashes TCP stack
843790Jun 22 2007 — edited Jul 3 2007We have a problem in which, on certain machines, a Java Telnet client connected to a specific host will lock up, and crash the TCP stack of the machine it's running on.
On the test box we're running it on (Win2k running SE 1.6.0_01-b06), the problem occurs during initial negotiations: after the "NEW-ENVIRON" (including auto-logon) and "TERMINAL-TYPE" (a TN5250-specific type, probably "IBM-3477-FC") subnegotiations are completed, where negotiations would normally continue with will/do negotiations on "end of record" and "binary," it locks up trying to do a SocketInputStream.read(). At this point, the machine runs through a minute or more of alternating repeatedly between several seconds in which the mouse pointer is frozen, and several seconds in which it is responsive. By the time this is over, the TCP stack is toast.
On another test box that's also Win2k running SE 1.6.0_01-b06, everything works normally.
On a customer machine, it gets through the negotiation fine, but fails somewhat later in the session, with the same symptoms.
Has anybody here seen anything like this?