All,
I am facing the following incident -
Architecture setup: ActiveMQ running in JBoss; Camel used as MessageBus
1. High volume of messages are published to a Queue
2. My application consumes them and if they fail validation they are
DeQueued (goes to ActiveMQ.DLQ)
3. I can also see the messages persisted in the Database
(Table: activemq_MSGS; container: ActiveMQ.DLQ)
4. I notice that 64MB is default Queue size
5. Once the size of messages in ActiveMQ.DLQ crosses 64MB, I notice that my
Camel routes are frozen (unable to publish any more messages to Queues)
To replicate this I set the following in my broker-config.xml
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="1 kb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="1 mb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="1 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
and i can see the same above scenario occuring.
Does this mean -
(1) activeMQ expects enough free-memory-space in the DLQ before any
publisher can publish to a Queue?
(2) is the expectation that I tactically clear the DeQueued messages at
regular intervals?
(3) The 64MB size is specific for each Queue - but since ActiveMQ.DLQ is
generic/global queue that holds all rejected messages - its size should
always be < 64MB for other Queues to receive messages?
Would appreciate if some one can clarify my queries.
regards
D
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Query-around-ActiveMQ-DLQ-tp4666277.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
