On Wed, Mar 25, 2009 at 1:19 AM, Erik Drolshammer <erik-...@fjas.no> wrote:
> I don't want to use JDBC if I can avoid it. I thought I _had_ to after > reading http://activemq.apache.org/shared-file-system-master-slave.html. > > When I removed the JDBC-element and thus used KahaDB things seems to be > working again. Strange that the derbydb didn't work at all. (One message > dispatch per minute instead of 500 per second or so normally.) This is common when Derby is run inside the same JVM as ActiveMQ because Derby is very hard on the garbage collector. We recommend splitting Derby into it's own JVM if you want to use it. > Looks promising. Any idea when it will be released? The AMQ message store was released when ActiveMQ 5.0 came out and it is the default persistent mechanism in the 5.x version. It makes use of Kaha as the message reference store. I suggest trying the AMQ message store as it is incredibly fast: http://activemq.apache.org/amq-message-store.html > Thanks for you help. :) > > FYI; > When we have verified our setup properly I want to create a jira issue > suggesting documentation extensions. Until then, I use > http://wiki.community.objectware.no/display/smidigtonull/ActiveMQ+-+clustering+for+High+Availability > as scratch area. Great, let us know if there's anything you'd like to contribute to the documentation. Bruce -- perl -e 'print unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.apache.org/ Apache Camel - http://camel.apache.org/ Apache ServiceMix - http://servicemix.apache.org/ Blog: http://bruceblog.org/
