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 10:15:32 GMT
The following comment has been added to this issue:

     Author: Samisa Abeysinghe
    Created: Wed, 6 Oct 2004 3:14 AM
I was under the impression that this buffer problem is handled by the following logic in AXIS_TRANSPORT_STATUS
AxisTransport::getBytes(char* pcBuffer, int* pSize) metod of AxisTransport.cpp (or Axis2Transport.cpp
in new transport)

1. It only reads from channel 
if (0 <= m_iBytesLeft)

Hence no part of already read message is lost

2. It gives only the number of bytes requested by parser using following logic
        int iToCopy = (*pSize < m_iBytesLeft) ? *pSize : m_iBytesLeft;
        strncpy(pcBuffer, m_pcReceived, iToCopy);
        m_iBytesLeft -= iToCopy;
        m_pcReceived += iToCopy;
        *pSize = iToCopy;
I noticed that Xerces sends 49152 as *pSize.

Now the question is do we need to test this against total size of the message we have given
to parser (i.e. m_pcReceived)?

In my understanding, Xerces is always ready with *pSize buffer, no matter how much it has
alredy read using previous getBytes calls.
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 3:14 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