[
https://issues.apache.org/jira/browse/SYNAPSE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated SYNAPSE-156:
--------------------------------------
Attachment: synapse-proxy-session-proposal.patch
Asankha,
Basic idea is to keep all related objects in one place instead of having them
scattered around various connection contexts and to make sure the target bound
connection has a means of making its state known to the client bound one as
visa versa.
My ideas can easily be completely off-base, so take this patch for what it is
worth to you. The code is completely untested as I never succeeded in making
Axis2 kernel work for me.
Cheers
Oleg
> Unexpected Closed Chanel Exception in ClientHandler
> ---------------------------------------------------
>
> Key: SYNAPSE-156
> URL: https://issues.apache.org/jira/browse/SYNAPSE-156
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.QA.B.2
> Reporter: Ruwan Linton
> Assignee: Asankha C. Perera
> Fix For: 1.1.-RC1-B1
>
> Attachments: synapse-proxy-session-proposal.patch
>
>
> This is the last comment for the SYNAPSE-155 from Oleg,
> I think found the cause of the problem. ClientHandler closes output sink
> channel prematurely at the same time with the connection to the target
> server, while the ServerHandler is still busy sending the response content
> back the client. This is a separate issue from the original one. I think you
> should close this issue and open a new one specifically for the said problem.
> Oleg
> =======================
> /**
> * Process ready input (i.e. response from remote server)
> * @param conn connection being processed
> * @param decoder the content decoder in use
> */
> public void inputReady(final NHttpClientConnection conn, final
> ContentDecoder decoder) {
> HttpContext context = conn.getContext();
> HttpResponse response = conn.getHttpResponse();
> WritableByteChannel sink = (WritableByteChannel)
> context.getAttribute(RESPONSE_SINK_CHANNEL);
> ...
> if (decoder.isCompleted()) {
> if (sink != null) sink.close(); // oopsie
> ...
> }
> ...
> =======================
> Please see SYNAPSE-155 (https://issues.apache.org/jira/browse/SYNAPSE-155)
> for more details
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
