From: Alan M Webb <alan_webb@us.ibm.com>

Some other IRC timing wrinkles  showed up:

[1] If connect processing blocked in socket activation, then
    the watch dog saw the session as connected, and eventually
    tried to ping, but because the socket create was still
    blocked, it barfed on a null reference. This then drove
    reconnect. Changed the watchdog handler so that it only
    tries to ping connections that are connected and not pending.
[2] If the socket creation actually fails, then the connect and
    pending flags were reset. This resulted in the connection
    being retried at the earliest possible opportunity. The
    longer login-timeout is preferrable, so the status flags
    are not reset, and the failed login is eventually timed
    out.
[3] The Inter-connection interval is primed so that the first
    session can connect without delay.

0 files changed, 0 insertions, 0 deletions