persistent, or non persistent messages? you want to be careful using non-persistent messages and disabling producer flow control. also temporary destinations don't provide a backing store and everything is in memory. this means even for persistent messages you can run oom with PFC off.
you can use jconsole or visualvm to connect over JMX.might want to take a look at this page for more http://activemq.apache.org/jmx.html On Mon, Apr 29, 2013 at 10:27 AM, SledgeHammer <gro...@firstam.com> wrote: > Hi Christian, here is my complete config. Its pretty standard. FYI: I tried > bumping up the <systemUsage> > <memoryUsage> > <memoryUsage limit="64 mb"/> > </memoryUsage> > > to 128 mb, and I still get the error. I have producer flow control disabled > as you can see. How do I "check using jmx" in a Windows environment? I am > very new to ActiveMQ and have ZERO Java experience hah. > > > > > <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.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.conf}/credentials.properties</value> > </property> > </bean> > > > <broker xmlns="http://activemq.apache.org/schema/core"; > brokerName="localhost" dataDirectory="${activemq.data}" > schedulePeriodForDestinationPurge="5000"> > > > > <destinationPolicy> > <policyMap> > <policyEntries> > <policyEntry topic=">" producerFlowControl="true"> > > <pendingMessageLimitStrategy> > <constantPendingMessageLimitStrategy limit="1000"/> > </pendingMessageLimitStrategy> > </policyEntry> > <policyEntry queue=">" producerFlowControl="false" > gcInactiveDestinations="true" inactiveTimoutBeforeGC="5000"> > > </policyEntry> > </policyEntries> > </policyMap> > </destinationPolicy> > > > > <managementContext> > <managementContext createConnector="false"/> > </managementContext> > > > <persistenceAdapter> > <kahaDB directory="${activemq.data}/kahadb"/> > </persistenceAdapter> > > > > <systemUsage> > <systemUsage> > <memoryUsage> > <memoryUsage limit="64 mb"/> > </memoryUsage> > <storeUsage> > <storeUsage limit="100 gb"/> > </storeUsage> > <tempUsage> > <tempUsage limit="50 gb"/> > </tempUsage> > </systemUsage> > </systemUsage> > > > <transportConnectors> > > <transportConnector name="openwire" > uri="tcp:// > 0.0.0.0:25055?maximumConnections=1000&wireformat.maxFrameSize=104857600 > "/> > <transportConnector name="amqp" > uri="amqp:// > 0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=104857600 > "/> > </transportConnectors> > > > <shutdownHooks> > <bean xmlns="http://www.springframework.org/schema/beans"; > class="org.apache.activemq.hooks.SpringContextHook" /> > </shutdownHooks> > > </broker> > > > <import resource="jetty.xml"/> > > </beans> > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Memory-leak-tp4666300p4666398.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
