axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXISCPP-171) AxisBench test fails because xerces is being sent too much information
Date Wed, 06 Oct 2004 09:00:32 GMT
The following comment has been added to this issue:

     Author: Fred Preston
    Created: Wed, 6 Oct 2004 1:59 AM
Hi All,
This is my understanding of the AxisBench problem.  AxisBench fails when parsing the 78th
part of the response message.  The reason for this is because when xerces calls back the axis
socket receive in channel.cpp it is given the whole Rx'ed message which is too big for it
to handle in one go. Xerces only buffers the first 10 * 1024 bytes and discards the rest (apparently
information is available in the xerces call that indicates when this has happened).  Thus,
when xerces gets to the end of it's buffer it calls back on axis to receive more of the Rx'ed
message, but because the axis code did not store that part of the message that xerces could
not except and it has nothing left to read it returns nothing and then xerces throws an exception
because the buffer is empty and the parsing is incomplete.

Fred Preston.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXISCPP-171
    Summary: AxisBench test fails because xerces is being sent too much information
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis-C++
             XML parser abstraction layer

   Reporter: Fred Preston

    Created: Mon, 27 Sep 2004 9:05 AM
    Updated: Wed, 6 Oct 2004 1:59 AM
Environment: n/a

Hi All,
I've uncovered an error when running the AxisBench test.  It fails because xerces is being
sent too much information and it's internal buffers are overflowing.  I tried to raise a problem
with xerces, but they pushed the problem back because return information was not being used
by axis (axis code is continuing to add information to the xerces reader when it has flagged
that there is no more space available).

Fred Preston

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message