On 06/25/2015 09:14 AM, Erik Aschenbrenner wrote:
Dear Qpid users,
I'm having a client application which uses the Qpid JMS API to connect to an
AMQP broker.
Do you know what version of AMQP it is? e.g. is it AMQP 1.0?
Is it possibe that messages which were sent successfully (without any
errors) by the Qpid JMS API did not arrive at the brokers queue? I thought
that should not happen when using the AMQP protocol.
If the broker accepts the message, then it is responsible for ensuring
the message is kept until it can be delivered. If the message is not
persistent then it may be lost if the broker is restarted but shouldn't
otherwise. There may also be limits on broker queues that cause old
messages to be evicted if the limit is exceeded.
The JMS 1.1 API however has no way to do asynchronous but acknowledged
publication. So either you are blocking every publication until accepted
(the default for persistent messages), or you are sending messages
without the application ever being informed when they are accepted. In
the latter case, the connection could be lost after the last message was
sent but before it was received by the broker. However I would expect
the client to get an error in this case (it just would not know exactly
which was the last message successfully sent).
Some days ago I did a load test where I sent 400 messages to the brokers
request queue but I did not get the responses for 2 of the 400 messages.
Before and after the messages where sent there where no errors or anything
suspicious in Qpid logs.
I created a ticket for the service which runs the AMQP broker and they told
me, that the 2 messages did not arrive at the broker but I have serious
problems in believing this.
Maybe to broker only needed to long for creating the responses?
How can I make sure that my messages where really sent over the network?
Maybe by using wireshark?
Yes, capturing the traffic on the wire is the surest way of 'proving'
that a message was indeed sent (and indeed whether it was accepted or not).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
