Unsolicited delivery Message

[ayz6uem]

info

client version amqp-client 5.4.3

Describe the bug

查看服务器日志

2025-08-16 03:54:31.076,BasicConsume,220,200,d299d1fffe28c126-00000032-01ab87fe-50393b87d2775a45-9a648ada,amqp-cn-5yd3h19yi002,,,/172.17.75.23:45020,216366274934553696,"queue=o_timeout_close_order_delay_queue,consumerTag=sgen-1-2GCULXKYOjHePEzy",dingding_vhost,172.25.1.100,7f152d94f1791ede-58321a1,1755287671,,1755287671076000,1

2025-08-16 03:54:31.076,PushMessage,220,200,d299d1fffe28c126-00000032-01ab87fe-50393b87d2775a45-9a648ada,amqp-cn-5yd3h19yi002,"consumerTag=sgen-1-2GCULXKYOjHePEzy, deliveryTag=1, autoAck=N",o_timeout_close_order_delay_queue,/172.17.75.23:45020,216366274934553696,"msgId=689EE68A38374532005FC930,exchange=o_timeout_close_order_delay_exchange,routingKey=o_timeout_close_order_delay_routing_key,bodySize=82",dingding_vhost,172.25.1.100,7f152d94f1791ede-58321a1,1755287671,,1755287671076000,

客户端报错 Unsolicited delivery - see Channel.setDefaultConsumer to handle this case.

Reproduction steps

...

Expected behavior

how to resolve？

Additional context

No response

[michaelklishin]

@ayz6uem this is not a bug.

The message the client logs contains a decent hint: a channel has received a delivery while it did not have any registered (known) consumer for that delivery tag. This can happen when a delivery arrives immediately before the last consumer on the same channel was cancelled.

The suggested solution is registering a default consumer but it's enough to have a consumer with a suitable consumer tag.

[ayz6uem]

basicConsume

能否由客户端生成consumeTag，并且put到_consumers，然后再请求broker？

[acogoluegnes]

The application can pass in a non-null consumer tag indeed. The broker will use the consumer tag if any. It generates one if none is specified.

amqp-client 5.4.3 was released in 2018, please upgrade to the latest release (5.26.0 currently).