| Issue 3: | failed connection for remote host generates error message | |
| Back to list |
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
Apr 26, 2008
(No comment was entered for this change.)
Status:
Fixed
|