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 "nadir amra (JIRA)" <ax...@ws.apache.org> on 2007/02/12 06:58:05 UTC

[jira] Commented: (AXISCPP-481) Axis3 transport closes connection when using HTTP/1.1 even though Connection:close is not available

    [ https://issues.apache.org/jira/browse/AXISCPP-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472191 ] 

nadir amra commented on AXISCPP-481:
------------------------------------

Stage 1: 

I have put code in SVN that eliminated the looping counter, in which we loop 100 times if we do not receive any data.  Well, it always irked me that we had this in there since the only time we do not receive any data is when the connection has been closed, so there is no reason to loop.  I verified this via tracing. 

I also updated IChannel interface so that 

    virtual const IChannel&     operator >> (char * msg)=0;
    virtual const IChannel&     operator << (const char * msg)=0;

is now

    virtual int                 readBytes(char *buf, int bufLen)=0;
    virtual int                 writeBytes(const char *buf, int numBytes)=0;

This way one is easily able to detect when a connection is closed (receive lenght of zero) in addition to being much more efficent with no implicit reliance on some #defines for buffer sizes. 

Next stage would be to put code in to handle the detection of when one needs to reopen the connection and recover from unexpected errors. 

> Axis3 transport closes connection when using HTTP/1.1 even though Connection:close is not available
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AXISCPP-481
>                 URL: https://issues.apache.org/jira/browse/AXISCPP-481
>             Project: Axis-C++
>          Issue Type: Bug
>          Components: Transport (axis3)
>    Affects Versions: 1.5 Alpha
>            Reporter: Samisa Abeysinghe
>         Assigned To: Samisa Abeysinghe
>             Fix For: 1.5 Final
>
>
> The connection should not be closed when using HTTP/1.1 if Connection:close is not present.
> At the moment axis3 is closing the connection violating HTTP semantics.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org