axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (AXISCPP-114) AxisTransportException:Transport buffer is empty
Date Fri, 03 Sep 2004 15:33:50 GMT

   The following issue has been closed.

   Resolver: John Hawkins
       Date: Fri, 3 Sep 2004 8:32 AM

This issue was fixed. It was related to the change that occurred to have the transport as
non-blocking. The problem was that there was no code to handle when the socket came back empty
but still had some of the msg to come.
View the issue:

Here is an overview of the issue:
        Key: AXISCPP-114
    Summary: AxisTransportException:Transport buffer is empty
       Type: Bug

     Status: Closed
   Priority: Blocker
 Resolution: FIXED

    Project: Axis-C++
   Fix Fors:
             1.3 Beta
             1.2 Final

   Reporter: Alexei Dets

    Created: Tue, 20 Jul 2004 2:57 PM
    Updated: Fri, 3 Sep 2004 8:32 AM
Environment: RedHat Linux 9

Axis C++ client reports "AxisTransportException:Transport buffer is empty" after receiving
the responce from the server (also Axis C++, also version 1.2). The responce is valid, clients
that use Axis Java or PHP nuSOAP are working perfectly. This exception seems to depend on
the size of the responce message, it doesn't appear if the responce from the server is very
small (probably less than 1 or 2K).
To reproduce it just return something relatively big (10K probably will be enough) from the

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