qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Sim <g...@redhat.com>
Subject Re: released outcome
Date Mon, 29 Aug 2016 12:40:27 GMT
On 29/08/16 13:36, Matt Broadstone wrote:
> On Mon, Aug 29, 2016 at 8:31 AM, Gordon Sim <gsim@redhat.com> wrote:
>> I've raised a JIRA[1] and committed a fix.
> Oops, sorry about that.

No problem, I got the JIRA just before yours, and you beat me to the 
list. I marked yours as a duplicate.

>> Out of curiousity, what is your use case for consuming and releasing on an
>> LVQ?
> I think generally the same as for a normal queue: if a consumer receives a
> message it can't necessarily process at the time (maybe its a worker that
> is actually overloaded at the moment). I understand we could just republish
> the message, and had done so up until now, but I'm trying to move our
> internal code to a more consistent and generic rpc abstraction and this
> issue popped up for the one LVQ we are using.

I see, and so the LVQ mechanism is used to remove a redundant previous 
request when a new request message is sent?

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message