We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
首先感谢 workbunny 提供这么一款很好用的插件。使用【workbunny】RabbitMQ客户端,插件地址:https://www.workerman.net/plugin/67, 在消费者中如果有阻塞并超过一定时间,就会导致重复消费。
"workerman/webman-framework": "^1.5.0" "workbunny/webman-rabbitmq": "^1.0"
生产者:IndexController.php
workbunny rabbitmq配置:app.php
消费者:TestBuilder.php
通过日志可以看到,在出现错误前,是有消息消费成功并返回了 ACK。在出现错误后,相关进程重启,导致消息开始重新消费,以前返回的 ACK 似乎无效?RabbitMQ的控制台,始终显示有对应数量的信息处于 Unacked 状态。
The text was updated successfully, but these errors were encountered:
b73e855
fixed #11
fe00cef
No branches or pull requests
问题描述
首先感谢 workbunny 提供这么一款很好用的插件。使用【workbunny】RabbitMQ客户端,插件地址:https://www.workerman.net/plugin/67, 在消费者中如果有阻塞并超过一定时间,就会导致重复消费。
框架及插件版本
"workerman/webman-framework": "^1.5.0"
"workbunny/webman-rabbitmq": "^1.0"
复现代码
生产者:IndexController.php
workbunny rabbitmq配置:app.php
消费者:TestBuilder.php
关键日志打印
关键日志说明
通过日志可以看到,在出现错误前,是有消息消费成功并返回了 ACK。在出现错误后,相关进程重启,导致消息开始重新消费,以前返回的 ACK 似乎无效?RabbitMQ的控制台,始终显示有对应数量的信息处于 Unacked 状态。
The text was updated successfully, but these errors were encountered: