-
Bug
-
Resolution: Done
-
Major
-
AMQ 7.4.1.GA
-
None
-
None
-
-
+
-
Previously, if an OpenWire consumer disconnected and then reconnected to a broker, the broker failed to acquire credits, causing the consumer to run out of credits. This issue is now resolved.
-
Documented as Resolved Issue
-
Verified in a release
-
In an environment using OpenWire NMS clients and broker version 7.4.1, we see that messages get prefetched out to the consumer up to its default limit (1000); however, after the client acks all the messages (and the broker shows 1000 messages acked), the broker still reports the consumer is waiting on credits and reports current credits as NULL:
2020-02-26 12:44:06,228 DEBUG [org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl] ServerConsumerImpl [id=0, filter=null, binding=LocalQueueBinding [address=XXXX, queue=QueueImpl[name=XXXX, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID=739b6b51-f061-11e9-98c9-000f536b0260], temp=false]@376f976c, filter=null, name=XXXX, clusterName=XXXX739b6b51-f061-11e9-98c9-000f536b0260]] is busy for the lack of credits. Current credits = null Can't receive reference Reference[45099938419]:RELIABLE:CoreMessage[messageID=45099938419,durable=true,userID=ace4f982-5895-11ea-ab83-000f536b0260,priority=4, timestamp=Wed Feb 26 12:44:06 GMT 2020,expiration=Wed Feb 26 12:44:16 GMT 2020, durable=true, address=XXXX,size=1996,properties=...
Looking at a heap from the affected broker, the currentWindow for the consumer is "0" though there are no message references in deliveringRefs.
- is cloned by
-
ENTMQBR-3389 NMS / Openwire Client Runs Out of Credits Even though Broker Shows All Messages Acked
- Closed
- is related to
-
ENTMQBR-3339 The delivering count is wrong after reconnecting an openwire client
- Closed