djabberd: Dialback Failure in XML Parser

[Artur Bergman]

Probably depends on which parser you get from the parser pool and  
what state it is in.

Brad, we need tests that force the use of multiple parsers in the  
different states.

Artur


On Jul 1, 2006, at 10:44 AM, Martin Atkins wrote:

> It looks like the XML parsing module is sometimes bombing out when  
> doing dialbacks:
>
> -----------------
> DEBUG - New connection '56' from <undef>
> DEBUG - Connecting to '204.9.178.25' for 'sixapart.com'
> DEBUG - Set connection for queue to 'sixapart.com' to connection '56'
> INFO - 56 > <?xml version="1.0" encoding="UTF-8"?><stream:stream  
> to='sixapart.com' xmlns:stream='http://etherx.jabber.org/streams'  
> xmlns='jabber:server' xml:lang='en'  
> xmlns:db='jabber:server:dialback' version='1.0'>
> INFO - 56 > <?xml version="1.0" encoding="UTF-8"?><stream:stream  
> to='sixapart.com' xmlns:stream='http://etherx.jabber.org/streams'  
> xmlns='jabber:server' xml:lang='en'  
> xmlns:db='jabber:server:dialback' version='1.0'>
> DEBUG - We got a stream back from connection 56!
>
> DEBUG - Connection 56 supports dialback
> DEBUG - 56 sending '<stream:features></stream:features>'
> INFO - Generating diablack result for vhost s8n.me.uk
> DEBUG - Generated dialback result  
> 'i-61e2ecd02639c7b3a2802f9f9ecf13090c650782' using secret(of handle  
> 'i') 
> ='0.00320767772790020.7057045252498390.9667924507931150.42933786915674 
> 30.7168007179286630.2078640938432660.0522314573076770.4579624599145870 
> . 
> 3392655759469250.8473793792804790.804381807654970.6028387166741740.386 
> 8941784594710.9022135991312550.705337897715260.9090661577155470.993874 
> 5322183850.439894676244560.1063949849741660.374257112547841',  
> params='b1aa126d09c220fab28a633f02e587ad92528b4b|sixapart.com| 
> s8n.me.uk'
> DEBUG - 56 sending res 'i-61e2ecd02639c7b3a2802f9f9ecf13090c650782'
> INFO - 56 < <features xmlns='http://etherx.jabber.org/streams'/>
> INFO - 56 < <features xmlns='http://etherx.jabber.org/streams'/>
> DEBUG - New connection '57' from 204.9.178.8
> INFO - 57 > <?xml version="1.0" encoding="UTF-8"?><stream:stream  
> from='s8n.me.uk' id="57c40d410f0eaf8fb3b880bae12fa1905f72d816"  
> version='1.0' xmlns:db='jabber:server:dialback'  
> xmlns:stream="http://etherx.jabber.org/streams"  
> xmlns="jabber:server"><stream:features></stream:features>
> INFO - 57 > <?xml version="1.0" encoding="UTF-8"?><stream:stream  
> from='s8n.me.uk' id="57c40d410f0eaf8fb3b880bae12fa1905f72d816"  
> version='1.0' xmlns:db='jabber:server:dialback'  
> xmlns:stream="http://etherx.jabber.org/streams"  
> xmlns="jabber:server"><stream:features></stream:features>
> ERROR - 57 disconnected DJabberd::Connection::ServerIn=ARRAY 
> (0x901dc7c) because: Can't call method "_push" on an undefined  
> value at lib/DJabberd/XMLParser.pm line 58.
>
> WARN - 57 parsing *****
> <db:verify from='sixapart.com' to='s8n.me.uk'  
> id='b1aa126d09c220fab28a633f02e587ad92528b4b'>i-61e2ecd02639c7b3a2802f 
> 9f9ecf13090c650782</db:verify>
> *******
>
>
>
> DEBUG - DISCONNECT: 57
> --------------------
>
> I can't reliably recreate this, though. Sometimes it works and  
> sometimes it doesn't. It's not restricted to sixapart.com either;  
> I've seen it happen talking to livejournal.com and gmail.com too.
>
> Another error I've seen, which I've been unable to recreate for  
> this report, is a "not well formed" error; when this happens and it  
> prints out what it was trying to parse. This too happens during the  
> parsing of dialback verify.
>
>