You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Kevin Burton <bu...@spinn3r.com> on 2015/02/11 03:31:40 UTC
maxBrowsePageSize for non-persistent queues? Why not browse the whole thing?
Why does maxBrowsePageSize apply for non-persistent queues?
The data is in memory anyway, so what does it matter?
I’m trying to track down some queue data loss and dumping everything that
is in activemq would be valuable for debug purposes but I don’t want to do
anything that causes ActiveMQ to crash.
Further, other than disk IO , why does it matter anyway?
Kevin
--
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>
<http://spinn3r.com>
Re: maxBrowsePageSize for non-persistent queues? Why not browse the
whole thing?
Posted by Gary Tully <ga...@gmail.com>.
it is not always in memory, when memory is exhausted the temp store is
used by default for overflow.
On 11 February 2015 at 02:31, Kevin Burton <bu...@spinn3r.com> wrote:
> Why does maxBrowsePageSize apply for non-persistent queues?
>
> The data is in memory anyway, so what does it matter?
>
> I’m trying to track down some queue data loss and dumping everything that
> is in activemq would be valuable for debug purposes but I don’t want to do
> anything that causes ActiveMQ to crash.
>
> Further, other than disk IO , why does it matter anyway?
>
> Kevin
>
> --
>
> 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>
> <http://spinn3r.com>