Hi all,
We are using ActiveMQ 5.1.0 with durable topics. I conducted a load test and
concluded that ActiveMQ slows to a crawl when there are multiple orphaned
subscriptions (i.e. durable subscribers that are no longer used but are
accumulating pending messages). After deleting the orphaned subscriptions in
the admin interface, ActiveMQ became much faster. Now I am trying to limit
the number of pending messages so that we do not run into this situation. I
looked at http://activemq.apache.org/slow-consumer-handling.html and
modified activemq.xml as follows:
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" memoryLimit="5mb"/>
<policyEntry topic=">" memoryLimit="5mb">
<dispatchPolicy>
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
</policyEntry>
<!-- limit pending messages on "pes" topic -->
<policyEntry topic="pes">
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy
limit="10"/>
</pendingMessageLimitStrategy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
This did nothing. All orphaned subscriptions are still accumulating
messages. How do I fix it? Also, can somebody please explain systemUsage for
me? I am using the default configuration:
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="20 mb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="1 gb" name="foo"/>
</storeUsage>
<tempUsage>
<tempUsage limit="100 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
Clearly, this does nothing. The data directory is already 4GB and growing.
Also, what does the name="foo" refer to?
thanks in advance,
Eugene
--
View this message in context:
http://www.nabble.com/dropping-messages-tp21024057p21024057.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
