First, at timestamp 16:28:41.519, we get a block of 1297 bytes. This
block renders a rather unremarkable message display screen using a
subfile, using one Write To Display command that renders the screen, a
second WTD that ends immediately after the control characters, and a
Read MDT Fields command.
Then, at timestamp 16:28:42:222 (less than 3/4 of a second later), we
get a failed read on the socket. Specifically, the Java is.read(byte[]
b, int off, int len) on the socket is itself returning a -1 (which is
supposed to indicate an EOF), and no exception is being thrown.
Then, at timestamp 16:28:43.988 (over 1 3/4 seconds later) we try to
send a 13 byte (15 with the terminating IAC EOR) response.
Since this whole sordid affair has begun, I've been unable to force an
EOF on a Telnet socket with our hardware, not by killing the connection
in WRKTCPSTS, not by varying off the device, and not by physically
unplugging the Ethernet cable.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.