Unacked messages when using SimpleMessageListenerContainer about spring-amqp HOT 3 CLOSED

Would you mind to upgrade to recently released Spring AMQP 1.7.5?
There are some fixes in the SimpleMessageListenerContainer around consumers.

I wonder if your problem is covered with them as well.

Thanks for understanding

from spring-amqp.

Yes, there was a race condition with auto-recovered channels. This was fixed in 1.7.5.

If you can't upgrade for some reason, turn off automaticRecoveryEnabled in the clientFactory - Spring AMQP doesn't need it - it has had its own recovery mechanisms since day one.

Closing this for now; if you still experience a problem after upgrading (or turning off auto recovery) please reopen.

from spring-amqp.

Hi,

Just found this thread today, and I think we have the same issue - "Sometimes we have messages that stay unacked until we restart our service or we kill the connection via RabbitMQ console."
But the difference is I have consumer in RabbitMQ greater than the number of active consumer in PCF.

Here is the link in stackoverflow I just created.
https://stackoverflow.com/questions/63465726/pcf-rabbitmq-unacked-messages-in-queue

RabbitMQ 3.8.5
Erlang 22.3.4.3
spring-amqp:2.0.5.RELEASE
amqp-client:5.1.2

Thank you

from spring-amqp.