Issue 3: failed connection for remote host generates error message
Status:  Fixed
Owner:
Closed:  Apr 2008
Project Member Reported by tla...@gmail.com, Jan 9, 2008
What steps will reproduce the problem?
1. Start up client LOCAL
2. Start up client REMOTE
3. Have LOCAL connect to REMOTE, but have the connection for REMOTE fail.

What is the expected output? What do you see instead?

We expect it to handle the situation gracefully. Instead we get a
"ioloop.cc:195: somehow missed a tick? resetting timers" error messages.
Jan 9, 2008
#1 minister...@gmail.com
Client-side debugging:

connection.cc:450: do_read(8), state(LISTENING)
connection.cc:461: new incoming connection
connection.cc:261: conn 0x80be0d0 changing state to TLS_HANDSHAKE
connection.cc:395: handshake waiting
ioloop.cc:195: somehow missed a tick? resetting timers
connection.cc:450: do_read(10), state(TLS_HANDSHAKE)
tlsmanager.cc:152: auto-allowing cert due to prefs setting.
connection.cc:261: conn 0x80be0d0 changing state to CONNECTED
connection.cc:450: do_read(10), state(CONNECTED)
connection.cc:494: read -9 bytes
connection.cc:616: connection error: A TLS packet with unexpected length was received.
connection.cc:631: resetting connection.
connection.cc:261: conn 0x80be0d0 changing state to DISCONNECTED
Apr 26, 2008
Project Member #2 tla...@gmail.com
(No comment was entered for this change.)
Status: Fixed