activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sitsky <>
Subject Possible issue with Queue.start()
Date Tue, 23 Oct 2018 01:36:45 GMT

I have been looking in an application using ActiveMQ and have a situation
where a producer is blocked with this log message due to the temp usage
limit being hit:

[ActiveMQ Transport: tcp:///aaa.bbb.ccc.ddd:65119@64759] 82567721 INFO -
Usage(Main:temp:queue://aaabbb:temp) percentUsage=99%, usage=61771109932,
limit=61771104256, percentUsageMinDelta=1%;Parent:Usage(Main:temp)
percentUsage=100%, usage=61771109932, limit=61771104256,
percentUsageMinDelta=1%: Temp Store is Full (99% of 61771104256). Stopping
producer (ID:aaaaa-3:1:1:1) to prevent flooding queue://aaabbb. See for more info
(blocking for: 8512s)

In the past I have been able to use JConsole and update the broker's JMX
TempLimit value to a higher value to allow things to continue.

However on this occasion, the messages above when output again show that
the parent's limit has updated however the child's limit is unchanged.  So
it seems the broker's TempUsage does not know about the queue's TempUsage.
In looking at the code.. it seems a child Usage class has to call start()
in order for this parent -> children link to be established (and for limit
changes to be propagated down), but the Queue start() method doesn't call
systemUsage.getTempUsage().start() for some reason (or even just

Is this a bug?

DestinationView sadly does not expose setTempLimit() either so I am really

>From Queue:

    public void start() throws Exception {
        if (started.compareAndSet(false, true)) {
            if (memoryUsage != null) {
            if (systemUsage.getStoreUsage() != null) {
            if (getExpireMessagesPeriod() > 0) {

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message