Package: ejabberd Version: 2.1.5-3+squeeze2 Severity: grave We are migrating our XMPP infrastructure away from ejabberd, but it'd be not very nice not to let you know:
With mobile clients, such as Xabber on Android, we've seen plenty of cases of ejabberd losing messages. What seems to happen is that the mobile client loses connectivity (effectively going offline without telling the server). If the server now receives a message for the client, it seems to blindly forward it without waiting for acknowledgement. When the mobile client connects the next time, it won't get the message as the server deems it delivered and hence did not queue it for later delivery. I don't really have any more information or logs or traces, sorry. But I am sure this can be easily reproduced. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft <[email protected]> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
