please raise an enhancement issue in jira to track this. I guess we could use the temp store limits for this... ie: have the tmp file size increment the temp store usage, which would then block the producer.
On 20 December 2013 15:48, Sophia Wright <[email protected]> wrote: > Hi Garry, > > But there should be a upper limit on the file size because it may be > possible that a producer is sending messages using transaction and not able > to commit it ( may be because of some issue or may be some code glitches or > may be sending stuck in an infinite loop etc.) then it might fill the whole > hard disk and crashes the broker. > > May be in upcoming version you guys can fix this. > > Thanks, > Sophia > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Size-Limitation-for-tx-tmp-file-tp4675739p4675766.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
