[
https://issues.apache.org/jira/browse/QPID-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172517#comment-14172517
]
Hazel Bobrins commented on QPID-4648:
-------------------------------------
Found this from a google search, thread in ref said that we could use the get
available method to check if the sender is in a state to write to.
That does work up to a point, however, with non-durable messages you will
eventually get to a point where the available counter > 1 and the queue will
still block. For durable messages you get a framing error and don't block.
Really would be good to get a send() timeout.
> C++ client library Send() timeout
> ---------------------------------
>
> Key: QPID-4648
> URL: https://issues.apache.org/jira/browse/QPID-4648
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client
> Affects Versions: 0.20
> Environment: All
> Reporter: Connor Poske
> Assignee: Gordon Sim
> Fix For: Future
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The client C++ library does not implement a timeout for the send() function
> of the Sender class. This leads to the potential for indefinite blocking
> behavior.
> It would be nice for the C++ client to have a timeout parameter for send(),
> similar to the way the Java and Python clients do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
