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

RPC: Does Rabbot generate for replyTo? I don't receive any reply #187

Open
acarlstein opened this issue Feb 26, 2019 · 1 comment
Open

Comments

@acarlstein
Copy link

acarlstein commented Feb 26, 2019

Does Rabbot creates the unknown queue for replyTo for which our consumer will use to reply back the answer? Or do we have to generate it and provide it?

In RabbitMQ, for RPC, we indicate which queue our request will be sent by providing the routingKey.

var options = {
    type: 'request',
    routingKey: 'routing.key.to.queue',
    contentType: 'application/json',
    correlationId: require('uuid').v4(),
    body: {
      id: 1234,
      fibonacciNumber: 8
    },
    timeout: 60000,
    replyTimeout: 60000,
  };

However, I don't see in the documentation of rabbot if we require to provide a replyTo property with a queue randomly generated that later to be consumer should be destroyed as shown in this diagram:

rabbit-mq-rpc-diagram

I can receive the message sent to the queue, consume it, and send a reply to the replyTo provided.
However, I don't get anything back.

@acarlstein acarlstein changed the title RPC: request: Does Rabbot creates the unknown queue for replyTo? RPC: request: Does Rabbot generate for replyTo? I don't receive any reply Feb 27, 2019
@acarlstein acarlstein changed the title RPC: request: Does Rabbot generate for replyTo? I don't receive any reply RPC: Does Rabbot generate for replyTo? I don't receive any reply Feb 27, 2019
@zlintz
Copy link

zlintz commented Mar 28, 2019

This looks like a duplicate of issue #186

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

2 participants