axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Preston (JIRA)" <>
Subject [jira] Updated: (AXISCPP-558) Gracefully handle server side close of persistant connection
Date Mon, 21 Mar 2005 09:59:22 GMT
     [ ]

Fred Preston updated AXISCPP-558:

     Issue Type: Wish  (was: Bug)
        Version: unspecified
    Fix Version: unspecified

> Gracefully handle server side close of persistant connection
> ------------------------------------------------------------
>          Key: AXISCPP-558
>          URL:
>      Project: Axis-C++
>         Type: Wish
>   Components: Transport (axis3)
>     Versions: unspecified
>     Reporter: Tim Bartley
>      Fix For: unspecified
>  Attachments: http.patch
> With persistent connections, the server will typically time out an idle connection and
close it from it's end. Currently this results in an exception propagating to the user app
when it is safe to transparently close and reopen the connection.
> The attached patch adds a new interface that would allow optimized detection of server
side closed connections without sending any data. e.g. using recv(MSG_PEEK) - currently the
way HTTP transport works there is often some data (trailing white space) left in the connection
anyway which stops us seeing the connection as closed so that for now I've just left the channel
implementations of reopenConnection as simply "return false;".
> The main change is that on receiving a HTTPTransportException in HTTPTransport::flushOutput
during the send operations the connection will be reopened (if it hasn't alreayd been reopened
before) and the send retried.

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