Hmm, the error messages I'm used to seeing (from 5.8.0 and 5.10.0) look like the one in this page ( http://blogs.sourceallies.com/2014/10/activemq-memory-tuning/), which give lots of information about what limit is being hit. I guess that detailed info must have been added in a version after the one you're using. What version is that, anyway?
Can you post the full log message? Have you explored the JMX tree to see if there is any info to tell you how full your topics are? Obviously what information is available will vary based on what version you're running, so that might not help, but you should definitely check. On Aug 18, 2015 10:18 AM, "Daniel Israel" <disr...@liveops.com> wrote: > > Hi Tim, thanks for response. > > Flow control is enabled, and it's configured to fail if out of memory. As > noted below, the log lines in this version don't tell us which limit we're > exceeding, so we're running half blind :(. Knowing average topic size > would be helpful, but having individual topic size would be good. Right > now, looking at the producer side to see if there is some way to track. > > Raised the topic limit to 20mb and still had an issue. It's very hit and > miss. I can run for a week without issue, then when I get hit hard, it > falls over. > > > > > On 8/18/15, 5:58 AM, "tbai...@gmail.com on behalf of Tim Bain" < > tbai...@gmail.com on behalf of tb...@alumni.duke.edu> wrote: > > >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. > >> > >>
