operation queue.bind caused a channel exception not_found: no exchange

[Michelle Membrebe]

Hi!,

Encountering the error mentioned above. The federation exchange was registered but for some unknown reason (either after boot up or internet connectivity lost for a period of time), we get this error stating that the exchange was not found. Was wondering if anybody else encountered this and what could be the possible cause of the exchanges to be lost/deleted?

=ERROR REPORT==== 

Channel error on connection <0.12816.0> (10.XX.XX.XX:40313 -> 10.XX.XX.XX:5672, vhost: '/', user: 'xxx'), channel 1:

operation queue.bind caused a channel exception not_found: no exchange 'federation: xxx.exchange -> rabbit@mqconsumer A' in vhost '/'

=SUPERVISOR REPORT====

     Supervisor: {<0.17274.0>,rabbit_channel_sup_sup}

     Context:    shutdown_error

     Reason:     shutdown

     Offender:   [{nb_children,1},

                  {name,channel_sup},

                  {mfargs,{rabbit_channel_sup,start_link,[]}},

                  {restart_type,temporary},

                  {shutdown,infinity},

                  {child_type,supervisor}]

[Michelle Membrebe]

Note:
RabbitMQ version of the consumer is 3.5.7

RabbitMQ version of the producer   is 3.6.10

Both with Erlang 18.3

could this be a compatibility issue?

[Michael Klishin]

At least some manifestations of this error have been investigated for over a year. FWIW we see them quite a bit less

frequently with 3.7.x.

3.5.x has been out of support for a while now and 3.6.x went EOL last month. Erlang/OTP 18.3 has serious issues that

affect RabbitMQ [1]. So please upgrade at the first possibility [2][3].

1. http://www.rabbitmq.com/which-erlang.html

2. http://www.rabbitmq.com/changelog.html

3. http://www.rabbitmq.com/upgrade.html

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Michelle Membrebe]

Seeing as it has been investigated, is there any initial hypothesis on why this error is occurring?

On Thursday, June 7, 2018 at 1:41:40 AM UTC+8, Michael Klishin wrote:

At least some manifestations of this error have been investigated for over a year. FWIW we see them quite a bit less

frequently with 3.7.x.

3.5.x has been out of support for a while now and 3.6.x went EOL last month. Erlang/OTP 18.3 has serious issues that

affect RabbitMQ [1]. So please upgrade at the first possibility [2][3].

1. http://www.rabbitmq.com/which-erlang.html

2. http://www.rabbitmq.com/changelog.html

3. http://www.rabbitmq.com/upgrade.html

On Wed, Jun 6, 2018 at 1:46 PM, Michelle Membrebe <michelle...@gmail.com> wrote:

Note:
RabbitMQ version of the consumer is 3.5.7

RabbitMQ version of the producer   is 3.6.10

Both with Erlang 18.3

could this be a compatibility issue?

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michelle Membrebe]

Also saw that the federation exchange link were declared auto_delete = true

Base = #'exchange.declare'{exchange    = IntXNameBin,

durable     = true,

internal    = true,

auto_delete = true},

is there a way to set auto_delete to false without tampering with the rabbitmq-federation build?

[Michael Klishin]

If there was a plausible hypothesis we'd either prove it true or false by now.

Federation declares its exchanges for internal use. That's why the internal property is set to true.

You DO NOT want to make them non-autodelete because your apps cannot use them to begin with

(internal exchanges by definition are not accessible to clients).

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michelle Membrebe]

Hi Michael,

Correct me if i'm wrong as per my understanding of the process of how federation links are created:
When we register a new upstream, federated exchanges will be declared first before the federated queues?

[Michael Klishin]

Please start new threads for new questions.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.