Which JDK are you using? I mean, its producer, platform
it runs on and if it's a 32 or 64 bits version.
--
Questo messaggio è di carattere riservato ed è indirizzato esclusivamente
al destinatario specificato. L'accesso, la divulgazione, la copia o la
diffusione sono vietate a chiunque altro ai
The caveauts are here,
http://activemq.apache.org/replicated-leveldb-store.html , at the bottom of
the page.
For the rest, network of brokers and master/slave systems are complementary
solutions, aimed at different problems. Generally, a network of brokers
provides scalability, while master/slave p
Pure master/slave was removed as not production ready, and since they
already found something production-ready that would work with less effort
(leveldb).
I don't think they will develop the option of having similar functionality
with kahadb as well, what's the purpose of maintaining 2 separate sol
2014-10-15 9:09 GMT+02:00 deepakkumarpitti :
>
> 1. I was wondering if ActiveMQ provides some replication support from
> primary to failover brokers in real time so that even if I lose primary
> broker (and its persistent store), my failover broker can continue with
> it's
> own replicated state.
Look at http://activemq.apache.org/clustering.html and
http://activemq.apache.org/masterslave.html for the info you need. In a
nutshell, the master/slave(s) configuration is a structure to provide HA in
an active/passive fashion.
--
Questo messaggio è di carattere riservato ed è indirizzato esclu
Any system monitoring tool would go with your case, even a remote one. The
trick is: ActiveMQ (at least the recent versions, which are what I use)
won't open the broker ports until it gets the lock on the database, so just
by looking at where your port is open you can tell which server is working
a
Hi, there are 4 things to check out in your configuration.
1. The JMX configuration should be done from your wrapper file as someone
pointed out. Easier to mantain and goes with the documentation, but it's
still "optional" as there are several ways to implement it, and as
ActiveMQ's documentation l
Hi, we're running on a test server ActiveMQ 5.9.1.
The server is working as expected when producers and consumers are
connected; messages are correctly published. We now needed to monitor
the queues and the queued messages, prossibly reading the contents of
some of those. For this, I configure
