Author: buildbot
Date: Sun Mar 31 03:29:06 2013
New Revision: 856668
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/how-can-i-support-priority-queues.html
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified:
websites/production/activemq/content/how-can-i-support-priority-queues.html
==============================================================================
--- websites/production/activemq/content/how-can-i-support-priority-queues.html
(original)
+++ websites/production/activemq/content/how-can-i-support-priority-queues.html
Sun Mar 31 03:29:06 2013
@@ -93,6 +93,7 @@
<p>Since the message cursors (and client side) implement strict ordering of
priorities, it's possible to observe strict priority ordering if message
dispatching can happen from the cache and not have to hit the disk (i.e., your
consumers are fast enough to keep up with producers), or if you're using
non-persistent messages that never have to flush to disk (which happens by
default using the FilePendingMessageCursor). However, once you hit a situation
where consumers are slow, or producers are just significantly faster, you'll
observe that the cache will fill up (possibly with lower priority messages)
while higher priority messages get stuck on disk and not available until
they're paged in. In this case, you can make a decision to tradeoff optimized
message dispatching for priority enforcement. You can disable the cache,
message expiration check, and lower you consumer prefetch to 1 to ensure
getting the high priority messages from the store ahead of lower priority
messages:<
/p>
+
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
<destinationPolicy>
