[asterisk-bugs] [Asterisk 0015232]: [patch] XML parse errors related to buffer size, and not handled properly

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15232 
====================================================================== 
Reported By:                lp0
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15232
Category:                   Resources/res_jabber
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-30 07:23 CDT
Last Modified:              2009-05-30 11:33 CDT
====================================================================== 
Summary:                    [patch] XML parse errors related to buffer size, and
not handled properly
Description: 
I'm getting XML parse errors with a large roster. Decreasing the buffer
from 4096 to 512 doesn't help but increasing it to 65536 helps (even
although it's still split).

The connection should be dropped on an actual parse error (currently it
just times out because it still thinks it's connecting).
====================================================================== 

---------------------------------------------------------------------- 
 (0105789) seanbright (manager) - 2009-05-30 11:33
 https://issues.asterisk.org/view.php?id=15232#c105789 
---------------------------------------------------------------------- 
Could you please apply the attached patch and test?  It won't fix the
problem, but it will give me a better idea of where the problem is
occurring.  Please enable debugging with:

    core set debug 10

And upload a full log of the session.  You can either mask out the jids of
your roster members with xxxxx as you did before or I can mark the issue
private and you can upload the log without modification.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-30 11:33 seanbright     Note Added: 0105789                          
2009-05-30 11:33 seanbright     Status                   new => feedback     
======================================================================