Bruce Snyder wrote:
On Tue, Mar 24, 2009 at 1:17 AM, Erik Drolshammer <erik-...@fjas.no> wrote:
Bruce Snyder wrote:
On Mon, Mar 23, 2009 at 10:00 AM, Erik Drolshammer <erik-...@fjas.no>
wrote:
It seems this setup use DerbyDB and not Kahastore. Is this the only option?
Are there alternative setups that I might try?
Yes, the journaledJDBC element will use Apache Derby by default, but
you can specify a bean to use as the datasource in the activemq.xml so
that you can use whatever database you prefer.
Other persistence options include non-journaled JDBC as noted here:
http://activemq.apache.org/persistence.html#Persistence-JDBCPersistencewithoutJournaling
If you're using JDBC-based persistence, then you should look at using
JDBC master/slave:
http://activemq.apache.org/jdbc-master-slave.html
Another persistence option is Kaha persistence as described here:
http://activemq.apache.org/persistence.html#Persistence-KahaPersistence
With this style of persistence, you should use the KahaDB master/slave:
http://activemq.apache.org/kahadb-master-slave.html
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 the default persistence mechanism in ActiveMQ 5.x. If you're
using this style of persistence, then you should be using the shared
filesystem master/slave:
http://activemq.apache.org/shared-file-system-master-slave.html
Looks promising. Any idea when it will be released?
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.
--
Best regards,
Erik Drolshammer
