You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by "Sahan Gamage (JIRA)" <ji...@apache.org> on 2006/01/25 04:19:14 UTC

[jira] Assigned: (AXIS2C-23) HTTP transport does not seem to take into account the content-lengh/chunk size

     [ http://issues.apache.org/jira/browse/AXIS2C-23?page=all ]

Sahan Gamage reassigned AXIS2C-23:
----------------------------------

    Assign To: Sahan Gamage

> HTTP transport does not seem to take into account the content-lengh/chunk size
> ------------------------------------------------------------------------------
>
>          Key: AXIS2C-23
>          URL: http://issues.apache.org/jira/browse/AXIS2C-23
>      Project: Axis2-C
>         Type: Bug
>   Components: core/transport
>     Reporter: Samisa Abeysinghe
>     Assignee: Sahan Gamage
>     Priority: Critical
>      Fix For: M0.3

>
> The read callback causes the server to hang at times when the parser tries to read more data when there are none.
> Though this looks to be a problem with the SOAP builder, the callback is called from within libxml2, and hence the transport callback impl method should know how to tell the calling party that there are no more data. I used a timeout as a hack. But this solution need to be more clean with the transport looking for the end of the stream in line with the protocol in operation and letting the calling party know that there are no more data (that is return an empty buffer)

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira