O, and I forgot to mention I also turned on async sends (jms.useAsyncSend=true)
Maarten_D wrote: > > I've now changed my activemq.xml to the listing below, made the session > transacted and set the acknowledge mode to SESSION_TRANSACTED. > > Things were going well for me for a while, with the system processing 3,2 > million messages without a hitch, and then everything stopped because the > first component in the chain got lots of these: > > javax.jms.InvalidClientIDException: Broker: broker - Client: > ID:rhost-59116-1263927611185-1:445 already connected from /127.0.0.1:56560 > > And for an hour now, since it stopped processing messages, the broker has > been eating up almost 100% of the cpu for some reason I can't quite fathom > (disk utilization is very low, and there is no message traffic passing > through the broker). > > <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 > http://mortbay.com/schemas/jetty/1.0 http://jetty.mortbay.org/jetty.xsd";> > > <bean > class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> > <property name="location" value="file:/etc/broker.properties" /> > </bean> > > <broker id="broker" useJmx="true" brokerName="${broker.name}" > start="true" xmlns="http://activemq.apache.org/schema/core"; > dataDirectory="${activemq.data}"> > > <destinationPolicy> > <policyMap> > <policyEntries> > <policyEntry queue=">" memoryLimit="32mb" > strictOrderDispatch="true" producerFlowControl="false"> > <pendingQueuePolicy> > <vmQueueCursor /> > </pendingQueuePolicy> > </policyEntry> > <policyEntry topic=">" memoryLimit="32mb" > producerFlowControl="true" /> > </policyEntries> > </policyMap> > </destinationPolicy> > > <managementContext> > <managementContext useMBeanServer="true" > jmxDomainName="org.apache.activemq" > createMBeanServer="true" > createConnector="false" > connectorPort="1100" > connectorPath="/jmxrmi"/> > </managementContext> > > <persistenceAdapter> > <kahaDB directory="${activemq.data}/${broker.name}" > journalMaxFileLength="32mb" > enableJournalDiskSyncs="false" > indexWriteBatchSize="1000" > indexCacheSize="1000"/> > </persistenceAdapter> > > <systemUsage> > <systemUsage> > <memoryUsage> > <memoryUsage limit="512mb" /> > </memoryUsage> > </systemUsage> > </systemUsage> > > <transportConnectors> > <transportConnector uri="nio://0.0.0.0:61616" /> > </transportConnectors> > </broker> > > <jetty xmlns="http://mortbay.com/schemas/jetty/1.0";> > <connectors> > <nioConnector port="61617"/> > </connectors> > <handlers> > <webAppContext contextPath="/admin" > resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true"/> > </handlers> > </jetty> > </beans> > -- View this message in context: http://old.nabble.com/50k-%2B-messages-stuck-in-queue-with-all-consumers-blocking-on-receive-tp27162095p27261393.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
