diff options
| author | Anders Svensson <[email protected]> | 2014-11-03 00:12:58 +0100 |
|---|---|---|
| committer | Anders Svensson <[email protected]> | 2014-11-03 12:16:57 +0100 |
| commit | 66d67762be1cf0a3b9ac068d597c6d8bdaf2e3d7 (patch) | |
| tree | 95485009ba0a503c5dfe24ff8af8f474c8da77c0 /lib/diameter/test | |
| parent | 3b51661f1f9f70cf820026cb345523c05aad2dfa (diff) | |
| download | otp-66d67762be1cf0a3b9ac068d597c6d8bdaf2e3d7.tar.gz otp-66d67762be1cf0a3b9ac068d597c6d8bdaf2e3d7.tar.bz2 otp-66d67762be1cf0a3b9ac068d597c6d8bdaf2e3d7.zip | |
Fix ignored connect timer
There are two timers governing the establishment of peer connections:
connect_timer and watchdog_timer. The former is the RFC 6733 Tc timer
and is used by diameter_service to establish an initial connection. The
latter is RFC 3539 TwInit and is used by diameter_watchdog for
connection reestablishment after the watchdog leaves state INITIAL. A
connecting transport ignored the connect timer since the watchdog
process never died, regardless of the watchdog state, causing the
watchdog timer to handle reconnection.
This seems to have been broken for some time.
Diffstat (limited to 'lib/diameter/test')
0 files changed, 0 insertions, 0 deletions