synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <>
Subject [jira] Commented: (SYNAPSE-527) Transports use TRANSPORT_NON_BLOCKING in an incorrect way
Date Sun, 29 Mar 2009 17:48:50 GMT


Asankha C. Perera commented on SYNAPSE-527:

I opened AXIS2-4196 [AxisEngine meddles with concerns of the transports, and creates a thread
when sending out a message] a couple of months back to fix this in Axis2. Although this is
one of the core classes of Axis2, a full review and fix is needed and the TransportNonBlockingInvocationWorker
removed. Another critical issue is the Axis2 definition of a client and server side.. With
Synapse, we are both, and this causes a lot of issues too

> Transports use TRANSPORT_NON_BLOCKING in an incorrect way
> ---------------------------------------------------------
>                 Key: SYNAPSE-527
>                 URL:
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 1.2
>            Reporter: Andreas Veithen
>            Priority: Minor
> 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

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