I'm trying to use TelnetClient(commons-net-3.1) with the reader-thread enabled,
but it sometimes hangs.
I tracked "__receiveState", and found that the state sometimes changes to invalid ones.
In threaded-mode, TelnetInputStream.__read(boolean mayBlock) is normally called only by TelnetInputStream.run().
But if the read-thread startup delays, it may also called by TelnetInputStream.read()
beacues the value of __threaded is still false.
example of hang-up pattern
__thread.start(); ... try to start read-thread
TelnetInputStream.read() ... _threaded is still false, so TelnetInputStream._read() is called.
// read-thread starts (before __read() above dosen't end )
TelnetInputStream.run( ) ... sets _threaded to true, and calls TelnetInputStream._read()
I think __threaded flag should be set to true just after __thread.start(),
not at the begining of run().
__threaded = true; // add
This problem may related to