[jira] Closed: (AXISCPP-222) infinite loop in XMLPaserExpat when it encounters bad XML

["Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>]

     [ http://nagoya.apache.org/jira/browse/AXISCPP-222?page=history ]
     
Samisa Abeysinghe closed AXISCPP-222:
-------------------------------------

     Resolution: Won't Fix
    Fix Version: 1.4 Alpha

The community decided to move the Expat based parser lib to graveyard due to this issue and some other related issues. If one gives rebirth to Expat based parser lib, this and other related issues should be reopened and fixed.

> infinite loop in XMLPaserExpat when it encounters bad XML
> ---------------------------------------------------------
>
>          Key: AXISCPP-222
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-222
>      Project: Axis-C++
>         Type: Bug
>   Components: Parser Library - Expat
>     Versions: 1.2 Final, 1.3 Beta
>  Environment: HP-UX with GCC compiler, Expat 1.95.7
>     Reporter: James Guido
>     Priority: Minor
>      Fix For: 1.4 Alpha
>  Attachments: XMLParserExpat.cpp.diff_w_v1.9
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira