Page MenuHomeDevCentral

Declare notification exchange as durable
ClosedPublic

Authored by dereckson on Mar 12 2016, 05:20.
Tags
None
Referenced Files
F3743686: D335.id.diff
Thu, Nov 14, 23:10
Unknown Object (File)
Wed, Nov 13, 01:52
Unknown Object (File)
Sun, Nov 10, 04:06
Unknown Object (File)
Sun, Nov 10, 01:57
Unknown Object (File)
Sat, Nov 9, 21:44
Unknown Object (File)
Sat, Nov 9, 01:32
Unknown Object (File)
Fri, Nov 8, 21:01
Unknown Object (File)
Fri, Nov 8, 20:30
Subscribers
None

Details

Summary

When the notifications exchange is created on RabbitMQ by our container
setup script, it receives a Durable: true feature. We mirror this
behavior when we declare the exchange.

This fixes the following issue:

Channel error: (406, "PRECONDITION_FAILED - inequivalent arg 'durable'
for exchange 'notifications' in vhost 'dev': received 'false'
but current is 'true'")

Test Plan

Run the client, check we're well connected to the broker

Diff Detail

Repository
rNOTIFCLI Notifications center CLI client
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dereckson retitled this revision from to Declare notification exchange as durable.
dereckson updated this object.
dereckson edited the test plan for this revision. (Show Details)
dereckson added a reviewer: dereckson.
dereckson edited edge metadata.
This revision is now accepted and ready to land.Mar 12 2016, 05:21
This revision was automatically updated to reflect the committed changes.