You are right, there are probably three issues here:

if the DMQ is somehow synchronizing with itself the deletion on TCP connection lost will not work at all
The TCP connection lost will be not synchronized with DMQ
If an entry was marked expired because of TCP connection lost, and a new REGISTER is received before the timer was run to delete it, it will update the registration

Regarding 1 - this is another topic, which we are looking into right now.
About 2, yes the logic could be changed to actually remove/unregister it right now. This would also fix the issue 3.
Will look also into that.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.