activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From SuoNayi <suonayi2...@163.com>
Subject Re:Clarifcation on KahaDB support for message priority is needed
Date Fri, 22 Mar 2013 06:44:00 GMT
Since the broker has the pending message cursor as well so your messages 
are reordered by the cursor of the broker at first.Your client may reorder the
messages again if prefetch is enabled.
The two pending message cursors are fully priority-support so you won't see 
the fifo order no matter if your messages are persistent or not.



At 2013-03-22 10:50:28,"Christian Posta" <christian.posta@gmail.com> wrote:
>If your messages are non-persistent, then they won't get stored to kahadb,
>and kahadb's indexes and the priority categories won't come in to play.
>Another level of priority is implemented in messages that "have been paged
>in" or are ready to be dispatched and are in memory (or were never stored
>to begin with).
>
>
>
>
>On Thu, Mar 21, 2013 at 3:52 PM, mikmela
><mikmela@yahoo.com<javascript:_e({}, 'cvml', 'mikmela@yahoo.com');>
>> wrote:
>
>> with prefetch size=1 going to 5o messages still maintains message
>> priority...
>> Based on your description I thought the number of reordered messages
>> correlated to prefetch  size, am I missing something? My messages are
>> non-persistent. Maybe, the limit on the number of reodered messages depends
>> on the  pending cursor size on the client?
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Clarifcation-on-KahaDB-support-for-message-priority-is-needed-tp4665014p4665034.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
>-- 
>*Christian Posta*
>http://www.christianposta.com/blog
>twitter: @christianposta
>
>
>-- 
>*Christian Posta*
>http://www.christianposta.com/blog
>twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message