When using the built-in producer to test A-MQ functionality (for example, PFC), memory usage statistics for the given queue become frozen and PFC never kicks in. This appears to be due to caching becoming disabled and seems to happen with a small message size. The default behavior of the activemq:producer seems to be to sent a text payload of around 15 bytes. If a larger message size is specified, PFC seems to kick in fine. I later verified the same behavior with an external producer and small payload.
JBossA-MQ:karaf@root> activemq:producer --user admin --password admin JBossA-MQ:karaf@root> dstat Name Queue Size Producer # Consumer # Enqueue # Dequeue # Forward # Memory % ActiveMQ.Advisory.Connection 0 0 0 2 0 0 0 ActiveMQ.Advisory.MasterBroker 0 0 0 1 0 0 0 ActiveMQ.Advisory.Producer.Queue.TEST 0 0 0 2 0 0 0 ActiveMQ.Advisory.Queue 0 0 0 1 0 0 0 TEST 1000 0 0 1000 0 0 69 JBossA-MQ:karaf@root> activemq:producer --user admin --password admin JBossA-MQ:karaf@root> dstat Name Queue Size Producer # Consumer # Enqueue # Dequeue # Forward # Memory % ActiveMQ.Advisory.Connection 0 0 0 4 0 0 0 ActiveMQ.Advisory.MasterBroker 0 0 0 1 0 0 0 ActiveMQ.Advisory.Producer.Queue.TEST 0 0 0 4 0 0 0 ActiveMQ.Advisory.Queue 0 0 0 1 0 0 0 TEST 2000 0 0 2000 0 0 69
- is related to
-
ENTMQ-2103 [A-MQ6, producer flow control, destination memory usage] destination memory usage incorrect after sendtimeout due to PFC.
- Closed