[
https://issues.apache.org/jira/browse/PROTON-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577557#comment-13577557
]
Rafael H. Schloming commented on PROTON-222:
--------------------------------------------
You shouldn't need to bother with the tracker or status. I don't believe those
calls will interact with the network at all. I think setting the outgoing
window to 1 should be all that is necessary as that will cause send to block
until the remote disposition has been seen.
> pn_messenger_send returns before message data has been written to the wire
> --------------------------------------------------------------------------
>
> Key: PROTON-222
> URL: https://issues.apache.org/jira/browse/PROTON-222
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c, proton-j
> Affects Versions: 0.3
> Reporter: Rafael H. Schloming
> Assignee: Ken Giusti
> Fix For: 0.4
>
> Attachments: transport.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
