Spring AMQP
  1. Spring AMQP
  2. AMQP-266

Catch and WARN Incompatible Queue Declarations

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Complete
    • Affects Version/s: 1.1.1
    • Fix Version/s: 1.2.0.M1
    • Component/s: None
    • Labels:

      Description

      Currently all queue declaration stops when an error is encountered declaring a queue that has 'inequivalent' argument settings.

      {#method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-message-ttl'for queue 'appinsight.topology...received the value '60000' of type 'long' but current is none
      

      Detect RabbitAdmin queue declarations that fail due to incompatible (inequivalent) arguments; log at WARN level and continue with remaining declarations.

      Perhaps this should be an option on RabbitAdmin, with the default being the existing behavior of failing.

        Issue Links

          Activity

          Hide
          Mike added a comment -

          +1 For fixing this. Some projects debug mode is 'tear your eyes out' too much.

          Show
          Mike added a comment - +1 For fixing this. Some projects debug mode is 'tear your eyes out' too much.
          Show
          Gary Russell added a comment - PR: https://github.com/SpringSource/spring-amqp/pull/85

            People

            • Assignee:
              Gary Russell
              Reporter:
              Gary Russell
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: