- Notifications
You must be signed in to change notification settings - Fork586
Channel Closing#1074
-
Describe the bugHello Guys. Exception: How can I fix that? Specs: Reproduction steps
Expected behaviorTo Handle the exception and purge the invalid messages of queue Additional contextNo response |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 1 comment
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
We cannot suggest much withoutserver logs. I'm afraid our team won't be setting up Apache Camel to reproduce and troubleshoot this. You can put together an executable example in a repo but logs and a traffic will likely be enough. My best guess right now is that you try to ack on a channel that's different from the channel on which you have received the delivery. That results in achannel exception. Whether that can result in an "application context closure" in Spring AMQP, I don't know, but doing so will result in a channel exception that renders the channel unusable. Double acking or acking when the consumer was set up to useautomatic acknowledgement would have the same effect. |
BetaWas this translation helpful?Give feedback.
All reactions
This discussion was converted from issue #1074 on July 17, 2023 19:11.