[AXISCPP-222] infinite loop in XMLPaserExpat when it encounters bad XML

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.2 Final, 1.3 Beta
• Fix Version/s: 1.4 Alpha
• Component/s: Parser Library - Expat
• Environment: HP-UX with GCC compiler, Expat 1.95.7
• Assignee: Unassigned
• Reporter: James Guido
• Created: 22/Oct/04 19:12
• Updated: 20/Dec/04 11:01
• Resolved: 20/Dec/04 11:01

Description

Code when encounters only one event in XML events stack, it checks if last event is CHAR data. If last event is CHAR data; then, code proceeds to parse more data. Infinite loop is triggered when CHAR is the last data in stream. Eventhough stream returns TRANSPORT_FINISHED, XMLParserExpat goes into an infinite loop requesting for more data to parse.

I accidently trigger the bug by setting the content-lenght smaller than message, then the web server clipped SOAP message. If Axis w/ Expat parser encounters a message that was clipped/truncated, it will go into infinite if CHAR data is last data in stream.

I am attaching the fix I used.

Issue Links

• is depended upon by: AXISCPP-178 Client crashes with Expat parser for message with more than 7580 characters