activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Does JMS priority work with “small" maxPageSize ?
Date Wed, 06 May 2015 00:39:06 GMT
No, I was referring to your statement that "due to message cursors, that it
won’t be executed until it’s read into the “maxPageSize window”."  I can't
speak to the ability to serve up messages that aren't in the cursor under
those two message stores, though I've never seen anyone refer to such an
ability.

Tim

On Tue, May 5, 2015 at 11:29 AM, Kevin Burton <burton@spinn3r.com> wrote:

> You mean my statement "KahaDB and LevelDB could probably move it to the
> head (I think) but the memory store can not…"
>
> On Mon, May 4, 2015 at 7:31 PM, Tim Bain <tbain@alumni.duke.edu> wrote:
>
> > What you describe matches what I've always understood based on answers
> from
> > people on here (and I've never heard anyone say that the behavior is
> > different for any of the data store types), but I can't claim any
> firsthand
> > knowledge so if that's not right hopefully someone else will say so.
> >
> > Tim
> >
> > On Mon, May 4, 2015 at 12:14 PM, Kevin Burton <burton@spinn3r.com>
> wrote:
> >
> > > Let’s say you have a queue with 1M items.. they are all low priority.
> > Then
> > > you add a high priority entry.
> > >
> > > I believe, due to message cursors, that it won’t be executed until it’s
> > > read into the “maxPageSize window”.
> > >
> > > Is this correct or does it depend on the underlying store?
> > >
> > > KahaDB and LevelDB could probably move it to the head (I think) but the
> > > memory store can not...
> > >
> > > --
> > >
> > > Founder/CEO Spinn3r.com
> > > Location: *San Francisco, CA*
> > > blog: http://burtonator.wordpress.com
> > > … or check out my Google+ profile
> > > <https://plus.google.com/102718274791889610666/posts>
> > >
> >
>
>
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> <https://plus.google.com/102718274791889610666/posts>
>

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