Could you please to interpret how the parameter affect the performance of ActiveMQ?
thanks a lot, Zhuran Li At 2012-03-21 22:54:14,"Dejan Bosanac" <de...@nighttale.net> wrote: >Thanks for closing the loop! > >Regards >-- >Dejan Bosanac >Senior Software Engineer | FuseSource Corp. >dej...@fusesource.com | fusesource.com >skype: dejan.bosanac | twitter: @dejanb >blog: http://www.nighttale.net >ActiveMQ in Action: http://www.manning.com/snyder/ > > > >On Wed, Mar 21, 2012 at 8:49 AM, Pvbouwel <peter.vanbou...@contribute.be>wrote: > >> To be clear for other people wanting to change the wait time for kahadb >> lock: >> dejanb his answer was 100 % correct. I had a typo in my configuration >> file. >> If you want to change the time-out just change persistenceAdapter in your >> activemq.xml to look like: >> >> >> >> The value of databaseLockedWaitDelay is in miliseconds so this >> configuration >> will wait 1 second before trying a new attempt to get the lock. >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/10-seconds-wait-time-for-kahadb-lock-tp4488418p4491519.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>
