Skip to content
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

No API to make a handle on a unique queue #78

Closed
ghost opened this issue Mar 29, 2017 · 1 comment
Closed

No API to make a handle on a unique queue #78

ghost opened this issue Mar 29, 2017 · 1 comment

Comments

@ghost
Copy link

ghost commented Mar 29, 2017

I tried to create an unique queue for my process and make a handler only for this queue as I have many queues in the system.
Am I missing something or API just doesn't provide this?

  1. Calling addQueue with 'MyQueueName', {exclusive: true, unique: 'id', subscribe: true}
  2. Calling bindQueue with my exchange, and 'MyQueueName' still binds the queue fine

Now I want to create my handler for this unique queue and handle called with {queue 'MyQueueName'} isn't getting any messsages for that queue. From what I investigated I would need to call it with {queue: 'UNIQUEID-MyQueueName'} but there is no API to get generated, unique queue name or id.

@arobson
Copy link
Owner

arobson commented Feb 18, 2018

@ghost - I've fixed this so that you can just handle based on the friendly name/alias. I've also updated the docs to reflect it.

You can see the new integration test that shows a handle wired to a unique queue using the friendly alias working here.

@arobson arobson closed this as completed Feb 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant