Ignore the trace in my last mail. On closer inspection, I see that my
code was doing a basic.qos on channel 0.

With that corrected:

1320850428494: <Tracer-8> ch#1 -> {#method<basic.ack>(delivery-tagf6, multipleúlse),null,""}
1320850428494: <Tracer-8> ch#1 -> {#method<basic.qos>(prefetch-size=0, prefetch-count=1, globalúlse),null,""}
1320850428533: <Tracer-8> ch#1 <- {#method<channel.close>(reply-code@6, reply-text=PRECONDITION_FAILED - unknown delivery tag 666, class-id`, method-id€),null,""}

- My client program acks with a non-existent delivery tag.

- Before the server responds to that, the client sends the basic.qos

- Because of the delivery tag issue, the server sends a channel.close to
signal the channel exception.

In my client program, the amqp_basic_qos call returns NULL when the
channel.close is received, to signal the error. The details of that
error are available by calling amqp_get_rpc_reply on the connection.

--
David Wragg
Staff Engineer, RabbitMQ
VMware, Inc.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 5 of 10 | next ›
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedNov 8, '11 at 2:35a
activeNov 10, '11 at 12:34a
posts10
users3
websiterabbitmq.com
irc#rabbitmq

People

Translate

site design / logo © 2022 Grokbase