Hi

Just need to confirm this...

My testing using the Java client via jruby
shows that using, for example,
nextDelivery(500) will always take at least
500 milliseconds and not return early if
a delivery could be take from the queue
immediately.

Ta Guy.

Search Discussions

  • Matthias Radestock at Jul 1, 2011 at 10:32 am
    Guy,
    On 30/06/11 06:51, Guy Boertje wrote:
    My testing using the Java client via jruby shows that using, for
    example, nextDelivery(500) will always take at least 500 milliseconds
    and not return early if a delivery could be take from the queue
    immediately.
    That shouldn't happen, and looking at the code I can't see how it would.
    Can you post some code to reproduce this?

    Regards,

    Matthias.
  • Guy Boertje at Jul 1, 2011 at 11:33 am
    Thanks for your reply,

    Humble apologies, this morning I refactored my investigative code and
    found that the method call does return early with a delivery.

    I had tried to look for any confirmation of this in the
    LinkedBlockingQueue javadocs but it was not explicit.

    Rgds,
    Guy
    On Fri, 2011-07-01 at 11:32 +0100, Matthias Radestock wrote:
    Guy,
    On 30/06/11 06:51, Guy Boertje wrote:
    My testing using the Java client via jruby shows that using, for
    example, nextDelivery(500) will always take at least 500 milliseconds
    and not return early if a delivery could be take from the queue
    immediately.
    That shouldn't happen, and looking at the code I can't see how it would.
    Can you post some code to reproduce this?

    Regards,

    Matthias.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedJun 30, '11 at 5:51a
activeJul 1, '11 at 11:33a
posts3
users2
websiterabbitmq.com
irc#rabbitmq

2 users in discussion

Guy Boertje: 2 posts Matthias Radestock: 1 post

People

Translate

site design / logo © 2022 Grokbase