diff options
| author | Anders Svensson <[email protected]> | 2014-05-19 09:10:00 +0200 |
|---|---|---|
| committer | Anders Svensson <[email protected]> | 2014-05-20 02:43:03 +0200 |
| commit | 6d087921e7608691ed5cd554484a13b961d3620f (patch) | |
| tree | c2000cd0d34479bbd56584bb91098ade1fda5ed2 /make/otp_release_targets.mk | |
| parent | 25237481ccccd3ddfa74582dc267632ad618ba30 (diff) | |
| download | otp-6d087921e7608691ed5cd554484a13b961d3620f.tar.gz otp-6d087921e7608691ed5cd554484a13b961d3620f.tar.bz2 otp-6d087921e7608691ed5cd554484a13b961d3620f.zip | |
Fix watchdog table leak
Commit ef5fddcb (diameter-1.4.1, R16B) caused the leak in the case of an
accepting watchdog with restrict_connections = false. It (correctly)
ensured the state remained at INITIAL but a subsequent 'close' message
to terminate the process was ignored since the state was not DOWN. In
fact, no 'close' was sent since there was no state transition or
previous connection: the former triggers the message from
diameter_service, the latter from diameter_watchdog. The message is now
sent to self() from the watchdog itself.
Send 'close' in the same way when multiple connections to the same peer
are allowed, to avoid waiting for a watchdog timer expiry for the
process to terminate in this case.
Diffstat (limited to 'make/otp_release_targets.mk')
0 files changed, 0 insertions, 0 deletions