Hi, Using a destinationPolicy for dealing with large messages (23Mb):
<policyEntry topic="LOCAL.ORATK.CFILE" producerFlowControl="true" memoryLimit="30mb"> <pendingQueuePolicy> <vmQueueCursor/> </pendingQueuePolicy> </policyEntry> My broker hangs on flowcontrol as the topic has reached the 30Mb boundary - why ? Sending just 1 message of 23Mb by splitting it into chunks of 10kb and offering them to a Camel File component. At the other end of a network-of-brokers a Camel File component is writing the chunks to disk. The only way to release the flowcontrol is to bounce the affected brokers. Why ? There is enough diskspace at the consumer-end, don't understand why flowcontrol is never released. The poor-man's solution by setting producerFlowControle=false and slowing down the number of chunks offered to the Camel-component works, but that is not a very scalable solution. Any ideas ? Thanks