New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is a conflict between amq-client and amq-protocol settings #26
Comments
amqp gem 1.1 is just around the corner. Thanks for reporting. |
In point of fact, the ordering of amqp/client and amqp settings does not matter. Below is the reverse of @temochka s example: |
Does anyone know a work around for this? |
Use amqp gem |
If you need to parse an amqp(s) URI, simply use |
amq-client
|
Excellent! Thank you both for the quick reply and for your excellent work on this gem. |
If
amq/settings
is loaded beforeamq/client
thenAMQ::Client::Settings.parse_amqp_url
will raise aNoMethodError
exception.This is caused by improperly referencing Ruby built-in URI module at line 139 which gets overridden by
AMQ::URI
defined in theamq-protocol
(which is not compatible with Ruby URI module).Steps to reproduce:
I. Create an empty project with following Gemfile and run
bundle install
:Produced Gemfile.lock is:
II. Run
bundle exec irb
and follow these steps:Let me know if you need any additional info about the issue. I’m not sure if it makes sense to send a pull request (since the lib is not supported anymore), but the current stable version of the
amqp
gem relies on bothamq-client
andamq-protocol
, so this might cause issues for others (as it did for us).The text was updated successfully, but these errors were encountered: