Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.3.0
-
None
-
Reproduced on Windows XP 32 bit and Fedora 12 64bit.
Description
Scenario:
1. Configure polling consumer (prefetch=0), with onMessage()-style processing, e.g. with Spring's DefaultMessageListenerContainer.
2. Restart broker.
3. Notice consumer does not consumer messages anymore.
In client application this may show up during short network interruptions as reconnect message in logs/console + processing stoppage.
See http://old.nabble.com/ActiveMQ-reconnect-issue-with-consumer.prefetchSize%3D0-td27574923.html for more context.
Attachments
Attachments
Issue Links
- duplicates
-
AMQ-2877 Failover and prefetch=0 can result in hung consumers if the MessagePull command is lost
- Resolved