According to the AMQP 0.9.1 spec if a queue is re-declared the following parameters should be checked: :durable, :exclusive, :auto_delete, :arguments and if an exchange is re-declaring then the following parameters should be checked: :type, :durable, :arguments Before this patch the entire parameters hash was being checked which caused valid paramters to raise an AMQP::IncompatibleOptionsError exception.
…s present (this is not the case when :nowait is used)
… condition. If we release the id on the close call, the client might re-use the id before the server sends a close_ok
This reverts commit ac459ef. We will figure CI timeouts later.
…patibility with 0.6.x and 0.7.x series We initiailly installed deprecation warning around July 2011, during final 0.8.0 development iterations. See http://rubyamqp.info/articles/08_migration/ to learn about migration path from 0.6.x and 0.7.x to 0.8.x and later releases.