Yes - those settings apply to the both FileCursor and Kaha (which is
used by the AMQStore). - can you share the configuration you are using?
KahaDB isn't the same as Kaha - we weren't very imaginative with names
Im afraid
On 19 Jan 2010, at 23:48, rideallday wrote:
Rob,
I'm seeing the exact same behaviour as Daniel,
So I would recommend the following
2. Try KahaDB - which - with the BTreeIndex - will not hit the
problems you are seeing with the Filecursor
however I am already using KahaDB as the persistenceAdapter.
Your advice seems to apply only to FileCursor, right? Can you please
clarify.
Most settings are at default values, as I am only in the evaluation
stage.
Thanks.
Nic.
--
View this message in context:
http://old.nabble.com/OOM-with-high-KahaDB-index-time-tp27217704p27234786.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/
