You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@qpid.apache.org by ft420 <ar...@gmail.com> on 2009/06/15 12:11:36 UTC

lvqtest sample code

Hi,

Please correct in case of any misinterpretation of the concept
Concept:
LVQ:
Msgs will be updated only if msgs are not acquired OR browsed yet.
LVQ_NO_BROWSE:
Msgs will be updated if msgs are not yet acquired. It can get updated even
if they are browsed.

After broker has been started whatever queueoption is applied first be it
lvq OR lvq_no_browse it remains same untill broker shutdowns no matter
howmuchever we change it programatically through queueoptions.

hence if lvqtest is tested by giving lvq option first then lvq_no_browse
does not work as desired and vice-versa.

Please let me know the solution to this problem
Thanks



-- 
View this message in context: http://n2.nabble.com/lvqtest-sample-code-tp3079538p3079538.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org

Re: lvqtest sample code

Posted by ft420 <ar...@gmail.com>.

Thanks Carl there is one more query regarding key::

Is it possible to set numeric key instead of string? 




Carl Trieloff wrote:
> 
> ft420 wrote:
>> Hi,
>>
>> Please correct in case of any misinterpretation of the concept
>> Concept:
>> LVQ:
>> Msgs will be updated only if msgs are not acquired OR browsed yet.
>> LVQ_NO_BROWSE:
>> Msgs will be updated if msgs are not yet acquired. It can get updated
>> even
>> if they are browsed.
>>
>> After broker has been started whatever queueoption is applied first be it
>> lvq OR lvq_no_browse it remains same untill broker shutdowns no matter
>> howmuchever we change it programatically through queueoptions.
>>
>> hence if lvqtest is tested by giving lvq option first then lvq_no_browse
>> does not work as desired and vice-versa.
>>
>> Please let me know the solution to this problem
>> Thanks
>>
>>
>>   
> 
> If you delete the queue and re-define it the behaviour will get changed. 
> This is true for any
> queue in the broker. No queues support dynamic reconfiguration
> 
> Carl.
> 
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/lvqtest-sample-code-tp3079538p3084333.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org

Re: lvqtest sample code

Posted by Carl Trieloff <cc...@redhat.com>.

ft420 wrote:
> Hi,
>
> Please correct in case of any misinterpretation of the concept
> Concept:
> LVQ:
> Msgs will be updated only if msgs are not acquired OR browsed yet.
> LVQ_NO_BROWSE:
> Msgs will be updated if msgs are not yet acquired. It can get updated even
> if they are browsed.
>
> After broker has been started whatever queueoption is applied first be it
> lvq OR lvq_no_browse it remains same untill broker shutdowns no matter
> howmuchever we change it programatically through queueoptions.
>
> hence if lvqtest is tested by giving lvq option first then lvq_no_browse
> does not work as desired and vice-versa.
>
> Please let me know the solution to this problem
> Thanks
>
>
>   

If you delete the queue and re-define it the behaviour will get changed. 
This is true for any
queue in the broker. No queues support dynamic reconfiguration

Carl.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org