Ive raised a PR with some fixes in, see
https://github.com/apache/activemq-artemis/pull/901. This should make the
failover quicker in some scenarios. You can also make some configuration
changes like so:
Configure the cluster connection to time out quickly
2500
5000
And
And what happens when you take Claus's suggestion and run "activemq start"
from the bin directory instead of invoking java directly?
Calling java yourself isn't recommended for someone just getting started
with ActiveMQ. In fact, it's not recommended for anyone at all unless they
have a concrete
yes when i push the button start, it no longer running...
and the ports are not open too..
Atually i had experience to running this ActivemQ at 32bit Window computer
before.
but when i tryied in 64bit window and linux it just stopped in that moment.
i can't type anything
after stop this moment.
Hello!
I'm using ActiveMQ 5.10.0 client to connect to broker with failover protocol
and it fails to stop from Karaf console in case of massive sending job. Here
is the important part of a stacktrace:
17:31:17,254 | WARN | pool-47-thread-5 | FailoverTransport|
sport.failover.Failov
