Here's my setup using 5.4.0 <destinationPolicy> <policyMap> <policyEntries> <policyEntry topic=">" producerFlowControl="false" memoryLimit="1mb"> <pendingSubscriberPolicy> <vmCursor /> </pendingSubscriberPolicy> </policyEntry> <policyEntry queue=">" producerFlowControl="false" memoryLimit="1mb" useCache="false"> <!-- Use VM cursor for better latency For more information, see: http://activemq.apache.org/message-cursors.html <pendingQueuePolicy> <vmQueueCursor/> </pendingQueuePolicy> --> </policyEntry> </policyEntries> </policyMap> </destinationPolicy>
I'm not sure if it will solve your database storage issue, but you are describing similar problems we were getting. Restarting activeMq was the only other way we got the stuck message to be comsumed from the queue. -- View this message in context: http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-tp3244342p3248626.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.