Later versions give a few addition stats (such as average message size) via JMX, but that won't help you till that upgrade in production is complete.
Do you have producer flow control enabled? The error you're getting doesn't match what I remember it being the last time I hit it, so I'm assuming you don't. PFC gives log lines that at least tell you exactly which limit you ran into, plus it'll avoid losing any messages (but it'll "hang" producers till messages are consumed), so you could enable it to better understand what's going on. Tim On Aug 17, 2015 1:45 PM, "Daniel Israel" <disr...@liveops.com> wrote: > > Hello All, > > I am tracking down a memory issue in AMQ. I am time to time seeing > exceptions like this: > > > Async error occurred: javax.jms.ResourceAllocationException: Usage Manager > memory limit reached > > > I can't tell if this is because I am exceeding the configured amount of > memory in SystemUsage, or if I am exceeding the amount of memory configured > per topic. > > I am using only Topics right now, and I had the memory limit set to 10mb. > The error doesn't direct me in any direction for this. I am using an old > version of AMQ (First step was to request upgrade to latest version. It's > in the works, but it might be a week or two before it's completed in > production) and I see changes in the source that give more details when > throwing this exception. Is there some historical record or log of > Topics? What I'd really like is to be able to see how often each Topic > gets and distributes a message and how big that message was. The dashboard > and Jconsole give me some information, but because Topics are delivered > then released, I don't have any information beyond how many were enqueued > and delivered. > > Is there any such animal available that would help me with this? Or > suggestions how to approach? Any help is appreciated. Thanks. > >
