[
https://issues.apache.org/activemq/browse/AMQ-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies updated AMQ-2657:
----------------------------
Priority: Major (was: Blocker)
Downgrading this to a major bug. I can't reproduce it - would like to know if
its possible to add an expiration to the messages.
Also - in 5.4 is the option to garbage collect unused destinations- which may
help.
Do you know the types of messages being enqueued ?
> temp-queue - no producer, no consumer -> messagecount
> ------------------------------------------------------
>
> Key: AMQ-2657
> URL: https://issues.apache.org/activemq/browse/AMQ-2657
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.1
> Reporter: Marcin Giedz
> Assignee: Rob Davies
> Fix For: 5.4.1
>
> Attachments: activemq.xml, jms1.png, jms2.png, jms3.png
>
>
> HI,
> I tried the latest snapshot 12.03.2010, several producers and consumers. No
> matter what I change in activemq.xml file I always end up with memorylimit
> and broker is "frozen". However today I found one really strange thing. Maybe
> this is something wrong with what JMX says but: several temp-queues with
> ConsumerCount=0, ProducerCount=0 but EnqueueCount was getting up and up and
> Dequeue was 0 all the time . This way MemoryPercentageUsage got to 100% and
> AMQ said again something like this:
> 2010-03-16 15:02:28,455 | INFO | Usage Manager Memory Limit reached on
> temp-queue://e0499daa-604e-227c-57c5-8a700a83d690:0. Producers will be
> throttled to the rate at which messages are removed from this destination to
> prevent flooding it. See
> http://activemq.apache.org/producer-flow-control.html for more info |
> org.apache.activemq.broker.region.Queue | ActiveMQ Transport:
> tcp:///127.0.0.1:46737
> My config file is attached. All producers and consumers use CMS -3.0.1. and
> 3.1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
