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

Implement a way for doing "Direct reply-to" #65

Open
fishtek opened this issue Jun 25, 2015 · 0 comments
Open

Implement a way for doing "Direct reply-to" #65

fishtek opened this issue Jun 25, 2015 · 0 comments

Comments

@fishtek
Copy link

fishtek commented Jun 25, 2015

Hello,

In RabbitMQ v3.4.0 they added a method for doing fast RPC called "Direct reply-to"

For users supposedly the server side of the RPC can remain the same (as long as it is publishing to the default exchange), the "magic" happens on the client side. However w/ the current version of Puka v0.0.7 I can not get this to work.

I have tried various versions of the rpc client:

Leaving the rpc_client mostly the same and only doing the wait on the self.consume_promise causes the client to simply hang. If I do wait on the publish first then i get back an exception:

  File "/usr/local/lib/python2.7/dist-packages/puka/connection.py", line 329, in wait
    raise_errors=raise_errors)
  File "/usr/local/lib/python2.7/dist-packages/puka/promise.py", line 35, in run_callback
    return self._promises[number].run_callback(**kwargs)
  File "/usr/local/lib/python2.7/dist-packages/puka/promise.py", line 135, in run_callback
    raise result.exception
puka.spec_exceptions.PreconditionFailed: {'class_id': 60, 'method_id': 40, 'reply_code': 406, 'reply_text': 'PRECONDITION_FAILED - fast reply consumer does not exist'}

I suspect it is because under the hood puka uses seperate channels for publishing and consuming? Perhaps this feature of RabbitMQ requires the same channel to be used when doing this type of RPC? If that is the case I wonder if there is any easy way to extend or modify Puka to support it?

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