Mercurial > prosody-modules
view mod_s2s_smacks_timeout/README.md @ 5820:742142f9771e
mod_groups_internal: Fix traceback when room doesn't exist
I'm not sure if it should even be included if it doesn't exist, but I'm not
currently sure how this situation occurs, so I'm implementing the lightest
possible fix for now.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 11 Jan 2024 15:53:18 +0000 |
parents | 78368d2865dd |
children |
line wrap: on
line source
--- labels: - Stage-Obsolete --- # Introduction ::: {.alert .alert-warning} This behavior has now been merged into [mod_s2s][doc:modules:mod_s2s] in trunk and is therefore obsolete when used with trunk. It can still be used with Prosody 0.12 to get this behavior. ::: This module closes s2s connections when [mod_smacks][doc:modules:mod_smacks] reports that a connection has not received a timely acknowledgement as requested, indicating that the connection is broken or the remote server is not responding. With the connection closed, the next stanza to be directed to that server will trigger Prosody to establish a new connection, instead of queueing it on the potentially broken connection. This should prevent messages from being stuck in a queue for a potentially long time before being bounced back to the sender as delivery failure reports. Normally the amount of time it takes for a broken connection to time out is determined by TCP. If this is deemed sensible behavior then it will likely be merged into Prosody itself somewhere.