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
Fix For: 1.1.-RC1-B1
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]
