[
https://issues.apache.org/jira/browse/SYNAPSE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vanjikumaran Sivajothy updated SYNAPSE-527:
-------------------------------------------
Fix Version/s: (was: 2.0)
FUTURE
> Transports use TRANSPORT_NON_BLOCKING in an incorrect way
> ---------------------------------------------------------
>
> Key: SYNAPSE-527
> URL: https://issues.apache.org/jira/browse/SYNAPSE-527
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.2
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Priority: Minor
> Fix For: FUTURE
>
> Attachments: synapse_sample_250.xml
>
>
> The TRANSPORT_NON_BLOCKING property is set on the message contexts for
> incoming messages by ServerWorker#createMessageContext (NIO HTTP transport)
> and AbstractTransportListener#createMessageContext. When the message is sent
> out, Synapse copies this property over to the message context for the
> outgoing message. This in turn has an impact on the threading behavior when
> the message is sent: depending on the value of TRANSPORT_NON_BLOCKING, the
> <send> mediator (more precisely the OperationClient) will invoke the outgoing
> transport in a separate thread. It is not clear why the transport that
> handles the incoming request should determine the threading behavior of the
> transport that sends the outgoing request to the target service.
> See also http://markmail.org/message/6iuslkueny24po73
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
