[
https://issues.apache.org/jira/browse/SYNAPSE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845307#action_12845307
]
Amila Chinthaka Suriarachchi commented on SYNAPSE-527:
------------------------------------------------------
Has this issue solved by now?
Currently Axis2 sets TRANSPORT_NON_BLOCKING only at here.
//if we don't do this , this guy will wait till it gets HTTP 202 in the HTTP
case
mc.setProperty(MessageContext.TRANSPORT_NON_BLOCKING, Boolean.TRUE);
mc.getConfigurationContext().registerOperationContext(mc.getMessageID(), oc);
in OutInAxisOperation which I believe don't get executed by synapse code.
> 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
> Priority: Critical
> Fix For: 1.3
>
> 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 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]
