On 28/09/18 10:49, ali hadi wrote:
Hello,
Our messaging topology uses a dispatch-router in front of many Java brokers.
In the case where all our brokers are down, we want to throw an exception
to the producer after a timeout. This is not possible with the idle-timeout
parameter since the producer is connected to the dispatch router which is
still responding.
Is there an equivalent to the JMS send timeout parameter or a way to not
let the producer hanging forever in proton C++?
No, but you can implement a timeout like that using the schedule()
method on the container. On sending a message, schedule a check on the
return tracker after the appropriate timeout. If when that fire the
delivery the tracker refers to has not been settled, you can take
whatever action needed to handle the timeout.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
