[jdev] if anyone is having problems with slow propogation for<x xmlns="MY_NAMESPACE" messages...

Wed Nov 30 14:37:29 CST 2005

Yeah. These are all muc messages, so it could be a muc-implementation
issue. I didn't test non-muc messages.

I actually don't mind the hack fix I'm using. I just wanted to put the
issue and the fix out there in case someone is having the same problem I
was.

-----Original Message-----
From: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] On Behalf
Of Peter Saint-Andre
Sent: Wednesday, November 30, 2005 3:30 PM
To: Jabber software development list
Subject: Re: [jdev] if anyone is having problems with slow propogation
for<x xmlns="MY_NAMESPACE" messages...

Kirschner, Larry wrote:
> 
> Just discovered something interesting with jabber1.4.3 and muc 0.6.0.
> 
> I've been having a problem with my jabber install where it's only 
> allowing messages at a rate of about 1 every 2 seconds and dropping 
> messages in between. I thought the problem was karma or maybe 
> something in the config.  What I finally figured out is that jabber 
> just doesn't like <message> messages that don't have a non-empty
<body> element.

You mean jabberd 1.4.3? In general, you should have no problems sending
messages without bodies -- the server should not even inspect the packet
to that level IMHO (unless it is doing some kind of content filtering). 
Certainly the specs don't differentiate between message-with-body and
message-with-no-body.

> What I had been sending were game-event messages that looked like
this:
> 
> <message>
>         <x xmlns="mtvn/games">
>         // game event payload here
>         </x>
> </message>
>                
> ...no matter what I tried, these message would start to propogate very

> slowly after I had sent the first few.
> 
> I finally tried a test where I sent regular messages with a <body> and

> those propogated normally. I experimented a bit and now I'm doing
this:
> 
> <message>      
>         // this dummy body element seems to make jabber happy
>         // it doesn't work if you just send <body/>
>         <body>1</body>
>         <x xmlns="mtvn/games">
>         // game event payload here
>         </x>
> </message>
> 
> ...and propogation speed is back to normal.

Odd. Sounds like an issue with jabberd 1.4.3. Are you sending these
messages through a MUC room? If so, it might be an issue with the
mu-conference implementation.

Peter

--
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml