Use JConsole to look at which consumers are connected (make sure at least one is!), how many messages they're currently working on (MessageCountAwaitingAcknowlegement), and whether the numbers appear to be increasing. For each queue, confirm whether the EnqueueCount is increasing; if it's not, the broker isn't accepting messages due to Producer Flow Control, or the producer isn't attempting to produce any for other reasons.
On Fri, Sep 19, 2014 at 3:55 PM, Kevin Burton <bur...@spinn3r.com> wrote: > We’ve been having this problem for a while now but it’s becoming more > apparent as we deploy in production. > > Essentially all messages in ActiveMQ get stuck until I restart it. Today > it took three restarts… then it just started working. > > Here’s my config: > > http://pastebin.com/F5L99biA > > We’re using LevelDB… the box seems to be idle while this is happening. > > There isn’t much data either. < 1GB… should all fit into memory. > > It’s entirely possible it’s the client … but I’m using the official > activemq client. > > I think I might try browsing the queue from the command line next time this > happens. > > Any other pointers to help track this down? > > -- > > 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> >
