You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Erik Aschenbrenner <ea...@icubic.de> on 2015/06/25 10:14:07 UTC
Lost of message lost possible in AMQP?
Dear Qpid users,
I'm having a client application which uses the Qpid JMS API to connect to an
AMQP broker.
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.
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?
Regards,
Erik
--
View this message in context: http://qpid.2158936.n2.nabble.com/Lost-of-message-lost-possible-in-AMQP-tp7627251.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Lost of message lost possible in AMQP?
Posted by Rob Godfrey <ro...@gmail.com>.
Which JMS AMQP 1.0 client / version are you using (the older
qpid-amqp-1-0-client-jms package - latest version 0.32, or the new
Proton-based apache-qpid-jms package - latest version 0.3.0)? Also
what delivery mode are you using in JMS - PERSISTENT or
NON_PERSISTENT?
Thanks,
Rob
On 25 June 2015 at 10:45, Erik Aschenbrenner <ea...@icubic.de> wrote:
>> Do you know what version of AMQP it is? e.g. is it AMQP 1.0?
> Yes, it is AMQP 1.0.
>
>
>
>
>
> --
> View this message in context: http://qpid.2158936.n2.nabble.com/Lost-of-messages-possible-in-AMQP-tp7627251p7627254.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Lost of message lost possible in AMQP?
Posted by Erik Aschenbrenner <ea...@icubic.de>.
> Do you know what version of AMQP it is? e.g. is it AMQP 1.0?
Yes, it is AMQP 1.0.
--
View this message in context: http://qpid.2158936.n2.nabble.com/Lost-of-messages-possible-in-AMQP-tp7627251p7627254.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Lost of message lost possible in AMQP?
Posted by Gordon Sim <gs...@redhat.com>.
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: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Lost of message lost possible in AMQP?
Posted by Robbie Gemmell <ro...@gmail.com>.
On 25 June 2015 at 09:14, Erik Aschenbrenner <ea...@icubic.de> wrote:
> Dear Qpid users,
>
> I'm having a client application which uses the Qpid JMS API to connect to an
> AMQP broker.
>
> 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.
>
> 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?
>
> Regards,
> Erik
>
Hi Erik,
I would echo everything Gordon already said (thanks!), but have some
quetions to add.
Are you using the newer qpid-jms-client (e.g.0.3.0), or did you return
to/stay using the older qpid-amqp-1-0-client-jms (e.g 0.32)?
You mention 2 messages out of the 400. Which 2 exactly? The last ones,
first ones, or some in the middle?
What delivery mode are you using?
Are you using transactions?
(I see Rob typed most of these questions quicker than I did...doh.
Sending anyway)
Robbie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org