Not at the moment out of the box. The Store Usage limits are broker wide so there is no way to limit the disk usage of a single destination. One thought would be to use non persistent messages for non important data.
An alternative avenue (which would require a bit of a code deep dive) would be to use two different persistence adapter instances by overriding the DestinationFactory on a BrokerService. You could provide your own implementation that would segregate important and non important destinations into different data stores with appropriate limits. In this way, you could get the required control of the disk usage. 2010/1/13 Daniel Kluesing <d...@bluekai.com> > Hi, > > I'm looking at ActiveMQ 5.3, with particular interest in the producer flow > control. Is there any way to have per-queue limits on the amount of disk > space a durable queue is using? I've seen the memory limit on the > destination policy, which looks to only apply to non-durable messages. > > In case that wasn't clear - I have two queues, importantData and > notImportantData, and I want to guarantee that if the consumer for the > notImportantData queue goes down it will only fill up, say, 1gig of disk > space so that importantData can continue to persist to disk even if the > notImportant consumer is down for a week. > > Is there a config setup that will allow this kind of control? > > Thanks, > > -Daniel > -- http://blog.garytully.com Open Source Integration http://fusesource.com
