synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] [Updated] (SYNAPSE-527) Transports use TRANSPORT_NON_BLOCKING in an incorrect way
Date Fri, 19 Sep 2014 04:41:34 GMT


Hiranya Jayathilaka updated SYNAPSE-527:
    Priority: Minor  (was: Critical)

> 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
>            Assignee: Andreas Veithen
>            Priority: Minor
>             Fix For: 2.0
>         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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message