activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From watcher <>
Subject Message stuck on queue
Date Tue, 07 Dec 2010 15:46:07 GMT

We are currently experience a problem with activemq version 5.4.0 
Every 2-4 days of testing we get 1 message stuck on the queue. 
We have approx 10 queues were we serialize a POJO onto each queue. 
We have no more than 1000 messages on each queue.

We have up to 5 consumers (slow consumers between 5secs and 1min) on each

Each client will wait forever on the queue until the queue is empty.

Our client connect with a prefetch = 1, we also tried value of 0

   <broker xmlns=""
destroyApplicationContextOnStop="true" useJmx="true">
			For better performances use VM cursor and small memory limit.
			For more information, see:
            Also, if your producer is "hanging", it's probably due to
producer flow control.
            For more information, see:
                <policyEntry topic=">" producerFlowControl="true"
                    <vmCursor />
                <policyEntry queue=">" producerFlowControl="true"
                  <!-- Use VM cursor for better latency
                       For more information, see:
            The managementContext is used to configure how ActiveMQ is
exposed in 
            JMX. By default, ActiveMQ uses the MBean server that is started
            the JVM. For more information, see: 
            <managementContext connectorPort="2011"
jmxDomainName="my-broker" />

            Configure message persistence for the broker. The default
            mechanism is the KahaDB store (identified by the kahaDB tag). 
            For more information, see: 
            <kahaDB directory="${activemq.base}/data/kahadb"/>
            The systemUsage controls the maximum amount of space the broker
            use before slowing down producers. For more information, see:
                    <memoryUsage limit="256 mb"/>
                    <storeUsage limit="1 gb" name="foo"/>
                    <tempUsage limit="300 mb"/>
            The transport connectors expose ActiveMQ over a given protocol
            clients and other brokers. For more information, see: 
            <transportConnector name="openwire" uri="tcp://"/>


        Uncomment to enable Camel
        Take a look at activemq-camel.xml for more details
  	<import resource="camel.xml"/>

        Enable web consoles, REST and Ajax APIs and demos
        Take a look at activemq-jetty.xml for more details 
    <import resource="jetty.xml"/>

two different setups 
server windows 2008 
client windows 7

server: windows server 2003
client : windows 7 

When we restart activemq service the message appears.

Is there anything that we can do to prevent this from happening?

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message