[SYNAPSE-527] Transports use TRANSPORT_NON_BLOCKING in an incorrect way

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.2
• Fix Version/s: FUTURE
• Component/s: Transports
• Assignee: Andreas Veithen
• Reporter: Andreas Veithen
• Created: 29/Mar/09 15:32
• Updated: 24/Sep/17 19:55

Description

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

Issue Links

• depends upon: AXIS2-4196 AxisEngine meddles with concerns of the transports, and creates a thread when sending out a message