Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <27534454.post@talk.nabble.com>
Date: Wed, 10 Feb 2010 09:14:30 -0800 (PST)
From: lucious <marcin.giedz@arise.pl>
To: users@activemq.apache.org
Subject: ActiveMQ - TempTopic/TempQueue makes MQ frozen during high traffic
 flow
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hello,

Here is ActiveMQ 5.3.0 with clients connected using openwire and CMS
activemqcp-3.0.1. Server is Intel Platform with 8GB RAM :
1) policyEntry for topic=">" and queue=">" set up to memoryLimit=20mb and
producerFlowControl="false"
2) memoryUsage limit="256 mb", storageUsage = 10gb, tempUsage = 10gb
3) transport openwire with ?wireFormat.maxInactivityDuration=0

and we use quite a lot TempTopic's and TempQueues ... what I found after
really heavy traffic that :

1) Heap memory usage in JMX console went above 256MB and ActiveMQ was frozen
-> 
2) in the console such messages appeared:

 INFO | Started SelectChannelConnector@0.0.0.0:8161                                                                                                                        
 INFO | Slow KahaDB access: Journal append took: 511 ms, Index update took 0
ms                                                                                            
 INFO | Slow KahaDB access: Journal append took: 542 ms, Index update took 0
ms                                                                                            
 INFO | Usage Manager memory limit reached on
temp-queue://42455840-0bb5-0101-49b1-304ecf24dbbd:2. 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                                                        
 INFO | Usage Manager memory limit reached on
temp-queue://924b8029-97ad-f8e2-32ff-52384d24558e: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                                                        
 

I also confirmed in JMX console that for Topic and Queue producerFlowControl
is disabled but for TempTopic and TempQueue is enabled.

My question is:
1) is it possible to disable producerFlowControl for TempTopics and
TempQueues?
2) maybe clients apps using CMS (cpp-3.0.1) do not do kind of
"confirmations" to Broker?
3) what can be done to improve this set up: of course memoryUsage can be
changed I mean set bigger but I'm really worried about this memory being
consumed and not released. 

Any comments on that? ;)

Many thanks,
Marcin
-- 
View this message in context: http://old.nabble.com/ActiveMQ---TempTopic-TempQueue-makes-MQ-frozen-during-high-traffic-flow-tp27534454p27534454.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.