Are you reaching your diskUsage threshold (see systemUsage)?

On Sunday, April 19, 2015, Kevin Burton <bur...@spinn3r.com> wrote:

> Interesting.  It’s already 1 in the connection configuration.  I assume you
> mean queuePrefetch as it’s named differently in the destination policy.
>
> On Sun, Apr 19, 2015 at 5:42 PM, Justin Reock <justin.re...@roguewave.com
> <javascript:;>>
> wrote:
>
> > Have you tried forcing prefetch to 1 as a destination policy?
> >
> > -Justin
> >
> >
> > On Apr 19, 2015 8:15 PM, Kevin Burton <bur...@spinn3r.com <javascript:;>>
> wrote:
> > I’m totally stumped on this bug ….
> >
> > Essentially, I have a queue that locks up and consumers in my main daemon
> > no longer consume messages from it.
> >
> > It’s basically dead.  If I restart my daemon, no more messages are
> > consumed.
> >
> > I can browse the queue, consume them from my desktop, but I can’t consume
> > them from my main daemon.
> >
> > I’ve done all the normal debugging. JMX shows there are plenty of
> messages
> > there.
> >
> > Messages just aren’t being sent to the broker.
> >
> > Here’s my major epiphany for the day, I can resolve this deadlock, but
> just
> > purging the queue.
> >
> > No daemons needs to be restarted, etc. Just purging the queue is enough
> to
> > kick off message processing again.
> >
> > Any idea what this could be? I’m willing to debug this, submit a patch,
> > etc. I’m just at a loss as to what could be happening.
> >
> > I think it has something do to with the queue growing too large.  Shallow
> > queues work fine.  Deep queues lock up and stop processing work.
> >
> > --
> >
> > 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>
> >
>
>
>
> --
>
> 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>
>

Reply via email to