[ejabberd] Losing messages to dead connections

Evgeny Khramtsov xramtsov at gmail.com
Sun Mar 23 08:57:14 MSK 2014


Sat, 22 Mar 2014 18:32:44 +0000
Raoul Duke <rduke496 at gmail.com> wrote:

> Before I move on I have a question: why does ejabberd not notice that
> the send to the "dead connection" failed?  i.e. if the other end is
> gone/dead and therefore not ACK-ing the TCP send from ejabberd then
> why doesn't ejabberd notice this and deem the message as undelivered?

Because the TCP connection is alive as reported by network layer. If
it's closed (as reported by network layer) ejabberd treats the user as
offline. On and on this question goes. Go to networking ietf wg and
blame them.


More information about the ejabberd mailing list