On 05/12/2011 07:40 AM, Ilyushonak Barys wrote:
Gordon,
thank you very much for the answer. It really helpful.
The case I would like to solve concern message producer written in C++. The
main thing - do not loose messages (at least once delivery). The case is the
following:
1. I would like to use async message sending on producer to increase
performance. In this case I expect qpid messaging API cache my messages in
memory buffer on the client (producer). I expect that qpid messaging API
deliver the messages from the buffer to broker in other thread than my program
(producer) works.
Yes, that is what it does.
2. I would like to cache qpid connection and session objects to increase
producer performance.
Not sure what you mean here. You mean you want to avoid recreating a
connection/session each time you need it?
3. I would like to use the reconnect=true feature from connection settings
4. I would like do not loose messages. That means I need to know the messages
exactly delivered to the broker, and the messages which didn't. If something
goes wrong I need to redeliver messages not delivered before.
You can track the buffered messages using the available() method on the
sender. Messages are removed in order so if you send 4 messages, then
when available drops to 3 you know the first messages has been confirmed.
5. I would like to determine the situation, when " something goes wrong" to
start recovery process.
That involves getting an exception (TransportFailure). Given that you
are using reconnect, this would mean that the retry logic has given up.
What would recovery consist of here for your case?
Actually I would like develop assured high performance C++ producer with at
least once delivery reliability.
-----Original Message-----
From: Gordon Sim [mailto:[email protected]]
Sent: Wednesday, May 11, 2011 8:09 PM
To: [email protected]
Subject: Re: Sender Capacity and error handling
On 05/11/2011 02:26 PM, Ilyushonak Barys wrote:
Gordon,
Thank you very much for quick response. We have decided to use
reconnect_timeout and close session on exception.
Could you please provide some best practice for error handling with messaging
API?
Hard to answer that without more understanding of the specific applications.
PS. I expected something like callback error handler and so on...
The API doesn't use callbacks at all at present (that style of interaction can
be layered on top). Any call on the API may fail if the connection is lost
and/or cannot be re-established. Catching these at some level and either
exiting or doing some application specific handling would be required.
Sorry I couldn't be more helpful. If I'm missing the point of the question
please push back.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
_______________________________________________________
The information contained in this message may be privileged and conf idential
and protected from disclosure. If you are not the original intended recipient,
you are hereby notified that any review, retransmission, dissemination, or
other use of, or taking of any action in reliance upon, this information is
prohibited. If you have received this communication in error, please notify the
sender immediately by replying to this message and delete it from your
computer. Thank you for your cooperation. Troika Dialog, Russia.
If you need assistance please contact our Contact Center (+7495) 258 0500 or
go to www.troika.ru/eng/Contacts/system.wbp
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
