Doesn't make any sense. You have producer flow control off, but you're asking about why you're running into producer flow control.
There are other things wacky about this config. Are you sure this is the activemq config you're broker is really using? On Tue, May 21, 2013 at 8:37 AM, Islam Mohamed < islam.moha...@isourceglobal.com> wrote: > I have a problem when it comes to the ActiveMQ. I need to know where > exactly > I can re-configure the Active MQ to avoid the following error. > > Note that I am using the ActiveMQ ver 5.5 on Ubuntu 11.10 > > Usage Manager Memory Limit (67108864) reached on queue://1000010. Producers > will be throttled to the rate at which messages are removed from this > destination to prevent flooding it. > > And her is my configurations > > > > > <beans > xmlns="http://www.springframework.org/schema/beans"; > xmlns:amq="http://activemq.apache.org/schema/core"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd > http://activemq.apache.org/schema/core > http://activemq.apache.org/schema/core/activemq-core.xsd";> > > <bean > > class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> > <property name="locations"> > > <value>file:${activemq.base}/conf/credentials.properties</value> > </property> > </bean> > > > <broker xmlns="http://activemq.apache.org/schema/core"; > brokerName="localhost" useJmx="true" dataDirectory="${activemq.base}/data" > destroyApplicationContextOnStop="true" > schedulePeriodForDestinationPurge="0"> > > > <destinationPolicy> > <policyMap> > <policyEntries> > <policyEntry topic=">" producerFlowControl="false"> > <pendingSubscriberPolicy> > <vmCursor /> > </pendingSubscriberPolicy> > </policyEntry> > <policyEntry queue=">" producerFlowControl="false" > maxPageSize="500" queuePrefetch="300" expireMessagesPeriod="0" > queuePrefetch="1"> > > </policyEntry> > </policyEntries> > </policyMap> > </destinationPolicy> > > > > <managementContext> > <managementContext createConnector="false"/> > </managementContext> > > > <persistenceAdapter persistent="true" useShutdownHook="false"> > <kahaDB directory="${activemq.base}/data/kahadb" > journalMaxFileLength="32mb"/> > </persistenceAdapter> > > > > <systemUsage> > <systemUsage> > <memoryUsage> > <memoryUsage limit="1 gb"/> > </memoryUsage> > <storeUsage> > <storeUsage limit="100 gb"/> > </storeUsage> > <tempUsage> > <tempUsage limit="1 gb"/> > </tempUsage> > </systemUsage> > </systemUsage> > > > > <transportConnectors> > <transportConnector name="openwire" uri="tcp://0.0.0.0:61616 > "/> > </transportConnectors> > > </broker> > > > <import resource="jetty.xml"/> > > </beans> > > > > > > THANKS, HAVE A GREAT DAY GUYS... > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Memory-Limit-67108864-tp4667286.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
