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

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15232 
====================================================================== 
Reported By:                lp0
Assigned To:                seanbright
====================================================================== 
Project:                    Asterisk
Issue ID:                   15232
Category:                   Resources/res_jabber
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     resolved
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:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-30 07:23 CDT
Last Modified:              2009-05-30 15:11 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).
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-30 15:11 svnbot         Status                   ready for testing =>
assigned
2009-05-30 15:11 svnbot         Status                   assigned => resolved
2009-05-30 15:11 svnbot         Resolution               open => fixed       
======================================================================