[PROTON-222] pn_messenger_send returns before message data has been written to the wire

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.3
• Fix Version/s: proton-0.4
• Component/s: proton-c, proton-j
• Assignee: Ken Giusti
• Reporter: Rafael H. Schloming
• Created: 06/Feb/13 15:00
• Updated: 07/Jan/16 11:32
• Resolved: 15/Feb/13 19:56

Description

Currently, pn_messender_send will block until the engine reports there are no queued messages being held. The problem arises because the queued message count only reports message data that is being held by the engine due to insufficient credit to send the messages. Messages may also be sitting in the transport's encoded frame buffer waiting to be written to the wire, and messages may also be held by the driver itself. This latter possibly is problematic given the current transport interface because there is no way for an application using the engine (in this case messenger) to know whether data is being held by the driver without introducing an undesirable coupling between the application and the driver implementation.

Issue Links

• is related to: PROTON-225 Redesign Transport interface such that Transport owns the in/out buffers rather than its client