[jdev] Empty <stream:features/>

Bob Phan bob at devianttechnologies.com
Tue Feb 17 11:52:23 CST 2004

On Mon, 2004-02-16 at 17:59, Robert Norris wrote:
> On Mon, Feb 16, 2004 at 04:42:36PM -0500, Bob Phan wrote:
> > Okay, a little progress update on the component library for perl for
> > jabber2.  It can now successfully authenticate using SASL and such.
> > I re-initiate the stream and the server returns this:
> > 
> > <stream:features xmlns:stream='http://etherx.jabber.org/streams'/>
> > 
> > Which most likely explains why when I try to bind to a domain,
> > the server debug output shows this:
> > 
> > ROUT: sx (io.c:189) decoded read data (33 bytes): <bind
> > name='logger'><log/></bind>
> > ROUT: sx (io.c:65) completed nad: <bind name='logger'><log/></bind>
> > ROUT: sx (chain.c:119) calling nad read chain
> > ROUT: sx (io.c:108) tag 12 event 6 data 0x80c1600
> > ROUT: Mon Feb 16 16:22:39 2004 router.c:736 invalid packet namespace,
> > dropping
> > ROUT: Mon Feb 16 16:22:42 2004 router.c:831 read action on fd 12
> > 
> > Since binding doesn't show up as a feature and all...
> Component binding doesn't show up as a feature because it predates
> stream features. Your problem stems from the (as the error messages say)
> your packets being in the wrong namespace.
> Either declare the component namespace on the stream header:
>   <stream:stream xmlns:stream='http://etherx.jabber.org/streams'
>                  xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'>
> Or on the packets themselves:
>   <bind xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'>
>     <log/>
>   </bind>
Thanks!  That was exactly the problem.  I didn't see any mention of
that namespace in the component doc you linked before.

> Take a look at the component protocol docs for more info. It may also
> help to run a j2 component (the resolver is nice and simple) in debug
> mode and watch the traffic that is passed back and forth.
Yes, that was very helpful.  I was looking for a component to mess
around with as an example before.

Thanks again for all your help.  I just finished up the library and
everything works now.  I sent a patch upstream to the maintainer, and
I'll shoot the list an email once it's been applied.

Now it's time to start work on the logging component.  I'll keep the
list informed on the progress of this component a little further
down the week.

Thanks again,
 * Bob Phan <bob at devianttechnologies.com>
 * Code Master General
 * Deviant Technologies Incorporated
 * (203)458-2312
 * http://www.devianttechnologies.com/

More information about the JDev mailing list