Paul Curtis wrote:
One of the problems we're having in deploying jabberd 2.0 is the 'c2s' disconnection issue. Right now, if a client sends invalid XML, the c2s disconnects from the router. This means that because of one bad client, ALL clients are bounced from the router.
Could you post some example XML which causes this behaviour ? Are there particular clients prone to doing this ?
I am willing to implement something, because without it, jabberd 2.0's 'c2s' is unusable in a large, enterprise deployment. Right now, this is the only complaint I've heard about Jabber and jabberd 2.0 ... frequent disconnections due to a client sending bad XML. Most of the problems are caused by duplicate attributes, especially in the case of messages that are stored offline.
This patch from Matthew Buckett:
http://www.marquard.net/jabber/patches/patch-util-nad.c
addresses one issue where jabberd2 was inserting an extra namespace in the XML retrieved from the offline store - c/f:
http://mail.jabber.org/pipermail/jabberd/2004-September/001997.html
The presence of the "xml:lang='en'" attribute may have been the trigger for the error, because it's quite hard to reproduce, but this may be unrelated to the broader c2s issue you describe.
However if bad XML in messages in the offline queue can cause problems, then it would also be worth fixing that in sm, because such messages can be inserted through the back-end database as well (i.e. not originating via c2s/s2s).
Regards Stephen
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mail.jabber.org/mailman/listinfo/jdev
