Hello Nageswararao. This email list is not for kafka spring plugin development. To exclude a Spring Kafka issue I suggest that you create a minimal test case where you create a producer and consumer, pause the consumer, publish a message with the producer, resume the consumer, and attempt to verify that your consumer can now poll for and read the message. If you're still seeing the issue then you can reach out again.
Regards, ________________________________ From: Nageswararao Edara <enr...@gmail.com> Sent: Friday, August 22, 2025 17:33 To: dev@kafka.apache.org <dev@kafka.apache.org> Subject: Kafka Start and Stop getting issue [You don't often get email from enr...@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] EXTERNAL SENDER. Do not click links or open attachments unless you recognize the sender and know the content is safe. DO NOT provide your username or password. Hi Team, While working on a project, I have a requirement to control Kafka listeners via a specific topic. During this, the pause() and resume() methods are working as expected. However, if I call stop() and then start() on a listener at runtime, any messages published in between are not consumed after the listener is started again. I am using *Spring Boot 3.5.0* and managing containers via the KafkaListenerEndpointRegistry class. Interestingly, if I restart the application and then publish messages, the listeners consume them without any issue. Could you please help me understand why the stop() and start() methods are not working as expected at runtime? Thank you, Nageswararao Edara. CONFIDENTIALITY NOTICE: This email message (and any attachment) is intended only for the individual or entity to which it is addressed. The information in this email is confidential and may contain information that is legally privileged or exempt from disclosure under applicable law. If you are not the intended recipient, you are strictly prohibited from reading, using, publishing or disseminating such information and upon receipt, must permanently delete the original and destroy any copies. We take steps to protect against viruses and other defects but advise you to carry out your own checks and precautions as Kambi does not accept any liability for any which remain. Thank you for your co-operation.
