axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Rheinheimer (JIRA)" <>
Subject [jira] Updated: (AXIS2-3202) Server sends close connection causes client to halt
Date Thu, 13 Sep 2007 20:23:40 GMT


Mike Rheinheimer updated AXIS2-3202:

    Attachment: patch.txt

> Server sends close connection causes client to halt
> ---------------------------------------------------
>                 Key: AXIS2-3202
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Mike Rheinheimer
>            Assignee: Mike Rheinheimer
>         Attachments: patch.txt
> Problem, solution, and patch provided by Nicholas Gallardo.
> In Asynchronous 2-way scenario, the client sends a request, the server responds with
a HTTP 202 in this HTTP connection, process to do it's work and send response back through
a callback via a different HTTP connection asynchronously.
> When the client that sends the first request (that gets the 202 response in async processing)
tried to re-use the socket while the server is still doing work in the background on that
socket, the http persist read for the next request doesn't start until the server finishes
it's work. The problem here is after the server sends a HTTP 202 back and the background work
process is not done, that particular HTTP connection gets stashed up, i.e. can't perform the
persist read until either the client is timed out (5 minutes currently) or the server work
process is complete.  We first saw this when they made the app sleep one minute to draw out
the background work and it was immediately noticeable.
> Switch threads on client dispatching.  This patch provides that functionality.

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:
For additional commands, e-mail:

View raw message