Replies: 1 comment 1 reply
-
You should not use You also should consider to upgrade to the latest Spring AMQP. We had some fix recently for stopping containers. If that still doesn't work for you, please, share some simple project we can reproduce on our side. Side note: GH comments allow us to post multi-line code snippet using triple back-ticks. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
I have a problem with an app i'm working on.
When my application gets an unexpected type of exception, i use
channel.basicNack(tag, false, true); SpringApplication.exit(context);
to stop the app and put the message in its original queue.
After that the application restarts and sometimes the application dies while starting with these kinds of logs :
I can see that the reason for it is an unresponsive consumer but i don't know how to fix it.
I've already tried to abort the channel, disable the restart main from spring devtools or disable the durable option of the Queue object that i'm using. I guess the problem comes from the way i'm stopping the channel but i can't manage to find the right way to do it.
I should mention that when the exception first arrives, i also get the logs of Waiting for workers to finish. and Workers not finished. except when i use channel.abort() but even with this i still get these at the restart.
I should also mention that i use the AcknowledgeMode : MANUAL
I'd love to get some help.
Thanks for your time
Have a great day !
Beta Was this translation helpful? Give feedback.
All reactions