On 10/11/2012 02:52 PM, Nitin Shah wrote:
Hi Gordon,
Thanks for your responses to both my questions. The receive side i.e.
that does the getNextReceiver() call and then fetches the message
does a session acknowledge as soon as the fetch returns.
The strange thing about my setup is that the sender is one thread on
a process ( linux) and the receiver is another thread on the same
process, so the data path is Process A to Broker via the Qpid Library
( I assume ) and then back to Process A. In my testing, the sends are
done for 20 packets and then stop and no more sends are done.
Right, your application does no more sends, but if the library
reconnects might it be resending any of these that are in doubt?
One way to rule that out is to do a Session::sync() in your test after
the last message is sent.
I see
that the receiver has received them and displayed the content for my
validation. Then I go in and kill the broker and in our system a
backup broker is started automatically. All users reconnect
automatically and the last 5 messages are received by the receiver in
Process A again. It does not matter how long I wait after the sends
are complete, may be minutes and it still repeats the messages.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
