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
TAMQOutputTransportFactory uses msg.properties['reply_to'] as a routing key for the response message, however TAMQTransport (used on the client side) populates the reply_to property with the queue kwarg. queue is required to be the name of a queue, not a routing key, and thus this pair of transports will only work if the response queue is bound to a key which is the name of a queue (typically itself).
In other words, it assumes a default exchange type, not a direct exchange, but this isn't made particularly clear (TAMQFactory even declares direct exchanges, but binds the queues to their names like a default exchange).
So this is really a request to support direct exchanges. I may add this later if it proves useful.
The text was updated successfully, but these errors were encountered:
TAMQOutputTransportFactory
usesmsg.properties['reply_to']
as a routing key for the response message, howeverTAMQTransport
(used on the client side) populates thereply_to
property with thequeue
kwarg.queue
is required to be the name of a queue, not a routing key, and thus this pair of transports will only work if the response queue is bound to a key which is the name of a queue (typically itself).In other words, it assumes a
default
exchange type, not adirect
exchange, but this isn't made particularly clear (TAMQFactory
even declaresdirect
exchanges, but binds the queues to their names like adefault
exchange).So this is really a request to support direct exchanges. I may add this later if it proves useful.
The text was updated successfully, but these errors were encountered: