SHOULD raise exception when durable, exclusive queue (spring-amqp/spring-rabbit) about spring-amqp HOT 4 CLOSED

What about that write a log for caution to programmers at this situation?

Well, I'd say that it is better to forward such a request to the RabbitMQ client directly.

Since com.rabbitmq.client.Channel.queueDeclare() doesn't throw any warnings, I don't see reason to overhead that on the Spring AMQP level.

When amqp-client will react somehow to that condition, Spring AMQP will propagate it transparently.

from spring-amqp.

Well, actually you have two different declarations for the same queue.
So, even if we throw IllegalArgumentException and you'd fix inconsistency, your second false for the exclusive will lead to similar PRECONDITION_FAILED.

Queue queueForTest2 = new Queue(queueName, false, true, false);

makes your test to pass.

To be consistent with the RabbitMQ spec, I don't see reason to break that rule and throw unexpected IllegalArgumentException , where all other clients just reconfigure request silently.

from spring-amqp.

yeah, I know that the second queue would better to replace with

Queue queueForTest2 = new Queue(queueName, false, true, false);

to pass the test or using just like that.
And you mean that we don't need to fix up the programmer's logical (I think it's logical) mistake?

Then, What about that write a log for caution to programmers at this situation?

from spring-amqp.

I see, I exactly understand what you saying.
Thanks for your lecture, it helps me alot :)

from spring-amqp.