I'm sorry to repeat my question, but I still haven't found a way to limit the size of both journal files and data files. I'm willing (actually, I want) to discard old message, but I have to guarantee that the disk usage would be bounded by something. Is that doable ?
rajdavies wrote: > > > On Jan 31, 2008, at 7:26 PM, dalin wrote: > >> >> >> rajdavies wrote: >>> >>> Store usage controls the maximum size of the AMQMessage Store >>> TempUsage is the maximum size of the store used for non-persistent >>> messages that may optionally overflow from memory awaiting dispatch >>> MemoryUsage is the maximum amount of memory the broker will use >>> >>> cheers, >>> >>> Rob >>> >>> http://open.iona.com/ -Enterprise Open Integration >>> http://rajdavies.blogspot.com/ >>> >> >> Are the settings enforced? For example, if I am running an embedded >> broker >> inside another java app and have set the max jvm heap size to be >> 512MB, but >> have set MemoryUsage to be 100MB. Will the broker only use at most >> 100MB of >> memory, or can it exceed that amount? >> -- >> View this message in context: >> http://www.nabble.com/StoreUsage%2C-TempUsage-and-MemoryUsage-tp15206526s2354p15212835.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > The broker makes a guess at how much space messages will use in the > JVM - based on the size of the message after its been serialized. If > you are using the vm://transport - messages aren't by default > serialized so it used the default - 8k as the message size. This means > that the broker should use 100mb or less of the available JVM space. > > > > cheers, > > Rob > > http://open.iona.com/ -Enterprise Open Integration > http://rajdavies.blogspot.com/ > > > > > -- View this message in context: http://www.nabble.com/StoreUsage%2C-TempUsage-and-MemoryUsage-tp15206526s2354p15258136.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
