ActiveMQ 5.x does not have the ability to write to multiple persistence
stores at once, so this is not possible in ActiveMQ 5.x using a single
broker. Depending on your requirements, it might or might not be possible
using multiple brokers.
Most people who ask about failover mean that persistent
we use mysql with activemq cluster. I can configure it to work with c3p0 when
db is down and retry but I would like to have activemq failover to kahadb
when database is down. Is this possible?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/is-it-possible-to-have-activemq
That's great news that it's reproducible, because that means you can set it
up in a test environment and attach a debugger to see what's happening and
why. I'd recommend setting a breakpoint on
http://activemq.apache.org/maven/5.12.0/apidocs/org/apache/activemq/store/jdbc/adapter/DefaultJDBCAdapter
Was there information that wasn't clear to you when you read the relevant
pages on the wiki (for example,
http://activemq.apache.org/failover-transport-reference.html and
http://activemq.apache.org/masterslave.html)? If you can be more specific,
we might be able to help you.
Tim
On May 2, 2017 10
Can you please give more details about your configuration, what your
scenario is that is resulting in a "number of messages [that is] too
large," and the specific aspect of performance that is the bottleneck in
your scenario? Your question is missing some pretty basic information that
would be need
If the broker is the master in a master-slave pair and the slave is up, the
slave will automatically become the new master and properly-configured
clients will automatically connect it and resume processing. Otherwise,
clients will generally attempt to reconnect until the broker comes back
up,thoug
