You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a configuration with only one queue is used, all handlers are called if any message is published.
If no queue is defined, the implementation creates a new queue per topic/handler and everything works fine.
The issue probably has to do with how the routingKey is passed on to the callback in amqp/subscriber.ts. If this were to pass on the routing key of the received message (msg.fields.routingKey) instead of the routing key that is passed into the subscribe function (and with which the binding is created) only the handlers for that specific routing key would get called.
If a configuration with only one queue is used, all handlers are called if any message is published.
If no queue is defined, the implementation creates a new queue per topic/handler and everything works fine.
The issue probably has to do with how the
routingKey
is passed on to the callback in amqp/subscriber.ts. If this were to pass on the routing key of the received message (msg.fields.routingKey
) instead of the routing key that is passed into the subscribe function (and with which the binding is created) only the handlers for that specific routing key would get called.The configuration I'm using:
The text was updated successfully, but these errors were encountered: