-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
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
Fence the MessageLisnterContainer restart once the ConcurrentMessageListenerContainer is stopped #3371
Milestone
Comments
I find this as a reasonable request. I'd like to have a fix for today's releases, but I don't see yet how to fix it. any chances that you can come up with a quick contribution? Thank you! |
I am having some idea on how to fix it. I will do it in a week. This is bit complex issue. |
Could you please review PR and give your comments. I will also check one more time, If I have to make further changes. |
artembilan
pushed a commit
that referenced
this issue
Jul 31, 2024
Fixes: #3371 Containers are not restricted from starting after ConcurrentContainer stopped or restarted. These changes would fix this issue. * Enhancements to fence container after ConcurrentContainer stops (cherry picked from commit 20696f2) # Conflicts: # spring-kafka/src/main/java/org/springframework/kafka/listener/AbstractMessageListenerContainer.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In what version(s) of Spring for Apache Kafka are you seeing this issue?
3.3
Describe the bug
ConcurrentMessageListenerContainer
with concurrency 2.KafkaMessageListenerContainer
from theConcurrentMessageListenerContainer
.KafkaMessageListenerContainer
.ConcurrentMessageListenerContainer
KafkaMessageListenerContainer
. This container would start running even thoughConcurrentMessageListenerContainer
has stopped. It is even holding the reference ofConcurrentMessageListenerContainer
.To Reproduce
I have modified the Junit in
org.springframework.kafka.listener.ConcurrentMessageListenerContainerTests
to reproduce.Expected behavior
I think, these containers should not be allowed to start once the
ConcurrentMessageListenerContainer
is stopped.The text was updated successfully, but these errors were encountered: