activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lucious <marcin.gi...@arise.pl>
Subject AMQ (5.3.0) with CMS-3.01 -> consumes all memory and stops clients and producers
Date Wed, 03 Mar 2010 17:50:27 GMT

Hello here is what we have:

1) AMQ -5 3.0 with the following configuration:
<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="localhost" useJmx="true" dataDirectory="${activemq.base}/data">

        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>
        <persistenceAdapter>
            <kahaDB directory="${activemq.base}/data/kahadb"/>
        </persistenceAdapter>
        <destinationPolicy>
            <policyMap>
                <policyEntries>
                <policyEntry topic=">" producerFlowControl="false"
memoryLimit="100mb">
                  <dispatchPolicy>
                        <strictOrderDispatchPolicy />
                  </dispatchPolicy>
                  <pendingSubscriberPolicy>
                        <vmCursor />
                  </pendingSubscriberPolicy>
                 <pendingDurableSubscriberPolicy>
                        <vmDurableCursor/>
                  </pendingDurableSubscriberPolicy>
                </policyEntry>
                <policyEntry queue=">" producerFlowControl="false"
memoryLimit="100mb">
                  <dispatchPolicy>
                        <strictOrderDispatchPolicy />
                  </dispatchPolicy>
                  <pendingQueuePolicy>
                        <vmQueueCursor/>
                  </pendingQueuePolicy>
                </policyEntry>
              </policyEntries>
            </policyMap>
        </destinationPolicy>

        <systemUsage>
            <systemUsage>
                <memoryUsage>
                    <memoryUsage limit="1024 mb"/>
                </memoryUsage>
                <storeUsage>
                    <storeUsage limit="10 gb" name="foo"/>
                </storeUsage>
                <tempUsage>
                    <tempUsage limit="10 gb"/>
                </tempUsage>
            </systemUsage>
        </systemUsage>

        <transportConnectors>
            <transportConnector name="openwire"
uri="tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=0"/>
        </transportConnectors>

System is being run with Xm=2048M

2) Producers and clients use CMS - 3.0.1 - we don't have any features added
to CreateFactory - all defaults are used.

Results:
1) during the day watch MQ via JMX I have: totalEnqueueCount=1193470,
totaldequeuecount=628130,totalmessagecount=1052834 - this I think is wrong
... shouldn't be like that: totalmessage+totaldequeue = totalenqueue?

2) memorypercentusage=73 and it's counting ... once it gets to 100% all is
frozen and in log file I get messages like this: 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         

quite strange as flow-control is disabled. 

3) watching Heap memory Usage I can see "saw chart" but it's going up and up
to 1GB and then is saturated (AMQ is frozen at that time).

4) the only thing I can do is to stop AMQ and restart ... however on
production is not a solution.

Maybe I have something wrong with configuration file? I'm also a little bit
confused about memoryLimit in topic/queue policy and memoryUsage. What
exactly these options do? I thought that if memoryUsage is 1GB and
percentUsage is 70% all messages are dropped into "file" and memory is
clean. Maybe I mixed this all up and it's not as I think it's?

Please help,
thx,
M.

-- 
View this message in context: http://old.nabble.com/AMQ-%285.3.0%29-with-CMS-3.01--%3E-consumes-all-memory-and-stops-clients-and-producers-tp27771356p27771356.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message