[
https://issues.apache.org/activemq/browse/AMQ-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51794#action_51794
]
Ivan S. Dubrov commented on AMQ-1940:
-------------------------------------
I had the same issue today.
We are running two AMQ brokers in network of brokers, each one talking to the
other one (the duplex is set to false). Under a high load after few hours I've
noted that one of our queues started growing on both nodes, several thousand of
pending messages in about 20 minutes (and the cursor memory usage was quite
large). After I accidentally stopped the second node, the network bridge
stopped on the first node and the queue size on the first node immediately
became "-8".
So in my case this probably somehow related to the instability of network of
brokers implementation, because if I disable the network connector the system
runs stable for several days under the load.
> Negative queue size (reproducible)
> ----------------------------------
>
> Key: AMQ-1940
> URL: https://issues.apache.org/activemq/browse/AMQ-1940
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Environment: Found on Windows but reproduced under Linux
> Reporter: Vadim Chekan
> Assignee: Rob Davies
> Priority: Critical
> Fix For: 5.2.0
>
> Attachments: Main.java, Picture 6.png, QueuePurgeTest.java.diff.txt
>
>
> When you "purge" queue from web admin console, it zeroes queue message
> counter. But if you have an active consumer at that time which
> pre-fetched messages than your consumer will keep sending ack as it
> process messages from its buffer. ActiveMQ will keep decrement counter
> upon receiving each ack. So when consumer is done queue will show
> MINUS<consumer buffer size>.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
