Shan Wang wrote:
Thanks for the reply, but this is the behaviour of broker, what will
this affect the producer? Will the producer simply gets notified that
its message has been accepted/rejected and close the session or maybe
it'll hang on there for a moment in certain cases.
Sorry, I misunderstood/misread the question.
If the message is rejected the client will be notified of the error and
the session will be closed. If you are publishing asynchronously, there
will be a slight delay between you sending the message in the client and
the client library then detecting that the session has been closed.
Producer has set the delivery property to PERSISTENT, I used --store-dir
to start the broker but I'm not sure if that means the queue is
persistent. Also the producer and broker are using direct exchange.
Are you creating the queue through the c++ client also (if so then
adding arg::durable=true to the call to queueDeclare() will make the
queue durable)? Or through some other means (e.g. qpid-config, in which
case specify --durable when creating the queue)?
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
