This should be fine. By default this will use a store cursor which can handle the overflow up to your storeLimit. As long as you are using either a store cursor or file cursor you can overflow messages on the broker to the message store or temp disk storage - just take care to not use vm cursors for this scenario. The producer flow control page has a small section on using a file cursor, but more details on how this works can be found at http://activemq.apache.org/message-cursors.html
If you still want producer flow control on, you may consider upping the memoryLimit on your destinations. Unless you explicitly specify it, the limit is 64 mb for both queues and topics I believe. On Sep 11, 2011, at 6:25 PM, bbansal wrote: > Thanks, > > I think I have disabled producer flow control in my config as > > <destinationPolicy> > <policyMap> > <policyEntries> > <policyEntry topic=">" producerFlowControl="false"> > <pendingSubscriberPolicy> > <vmCursor /> > </pendingSubscriberPolicy> > </policyEntry> > <policyEntry queue=">" producerFlowControl="false"> > </policyEntry> > </policyEntries> > </policyMap> > </destinationPolicy> > > Is this sufficient or I need to add some more config to disable > producer-flow-control for persistent queues. > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Backlog-data-causes-producers-to-slow-down-tp3806018p3806034.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
