axis-c-dev mailing list archives

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

     Author: Samisa Abeysinghe
    Created: Wed, 6 Oct 2004 3:42 AM
       Body:
I tried the AxisBench client with a AxisBench C++ service and it worked for 100 records. However
I was using the new axis2 transport.

When I tried to use the old axis transport it failed with the message:
AxisTransportException:Transport buffer is empty

This seems to be a problem with old transport. Please try this with new transport.


---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-171?page=comments#action_53747

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-171

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++
 Components: 
             XML parser abstraction layer

   Assignee: 
   Reporter: Fred Preston

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

Description:
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).

Regards,
Fred Preston


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.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


Mime
View raw message