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
the queue name was normal_queue for NORMAL_QUEUE_NAME
the NORMAL_ROUTING_KEY value was normal_routing_key
but the web show the normal_queue had not the routing key
Is it the Queue can not bind the exchange and routing key?
and the version 4.6.11 can set the arguements with
arguments={
'x-dead-letter-exchange': RabbitNameConfig.DLX_EXCHANGE_NAME,
'x-dead-letter-routing-key': RabbitNameConfig.DLX_ROUTING_KEY,
# 'x-message-ttl':10000 #
'x-message-ttl': int(
USER_TRANS_LIMIT_CLASS.TRANS_UNPAY_TIMEOUT_CLOSE_SECOND * 1000)
}
?
Any advice would be appreciated
Best,
hanhuihong
The text was updated successfully, but these errors were encountered:
Hi developer,
Is it the Queue can not bind the exchange and routing key?
and the version 4.6.11 can set the arguements with
arguments={
'x-dead-letter-exchange': RabbitNameConfig.DLX_EXCHANGE_NAME,
'x-dead-letter-routing-key': RabbitNameConfig.DLX_ROUTING_KEY,
# 'x-message-ttl':10000 #
'x-message-ttl': int(
USER_TRANS_LIMIT_CLASS.TRANS_UNPAY_TIMEOUT_CLOSE_SECOND * 1000)
?
Any advice would be appreciated
Best,
hanhuihong
The text was updated successfully, but these errors were encountered: