Hi, In our system, the activeMQ Queue's MemoryLimit is 64MB (default). We use the default message cursor (Store based).
We noticed that if the consumer were to publish multiple messages whose size exceed 100+MB, we motice that the consumer freezes indefintely. (I keep seeing this log) - the block time increases to 30 seconds every time 10:43:54,987 INFO [Queue] Usage(Main:memory:queue://queue.incomingEvents:memory ) percentUsage=0%, usage=0, limit=67108864, percentUsageMinDelta=1%;Parent:Usage (Main:memory) percentUsage=102%, usage=68532865, limit=67108864, percentUsageMin Delta=1%: Usage Manager Memory Limit reached. Producer (ID:XXXXX-189-50602- 1362737567247-3:12:2:1) stopped to prevent flooding queue://queue.incomingEvents . See http://activemq.apache.org/producer-flow-control.html for more info (block ing for: 1865s) 10:44:25,029 INFO [Queue] Usage(Main:memory:queue://queue.incomingEvents:memory ) percentUsage=0%, usage=0, limit=67108864, percentUsageMinDelta=1%;Parent:Usage (Main:memory) percentUsage=102%, usage=68532865, limit=67108864, percentUsageMin Delta=1%: Usage Manager Memory Limit reached. Producer (ID:XXXXX-189-50602- 1362737567247-3:12:2:1) stopped to prevent flooding queue://queue.incomingEvents . See http://activemq.apache.org/producer-flow-control.html for more info (block ing for: 1895s) Is this an expected behavior? Is the option to increase the Queue's MemoryLimit the right approach? We use activeMQ embedded in JBoss - so not comfortable in allocating 70% of heap to activeMQ. is using a File based cursor - the right approach? Does this gaurantee messages wil be available even if JBoss goes down? regards, D -- View this message in context: http://activemq.2283324.n4.nabble.com/Query-on-activeMQ-Queue-s-MemoryLimit-consumer-getting-blocked-tp4664494.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
