I have a network of several brokers where a couple nodes are producers to one
queue and a couple of nodes are consumers on this same queue. We are
testing high availability and in doing so pull the network cable on one of
the consumers. While this is happening there is a steady message rate on
th
I spent time last week trying to tune the parallel GC to prevent any
objects from reaching OldGen once the broker was up and running in a steady
state, to try to avoid expensive full GCs. My goal was zero full GCs for a
broker with 3-6 months of uptime, to prevent clients and other brokers from
fa
Per the documentation in the link from my first email, you'll see that
message when a destination is removed because it has been inactive (empty)
for the inactiveTimeoutBeforeGC period. So if you're getting that message,
it means that your destination has been empty for 60 seconds.
This is entire
Not much else. Once the master is elected, the slave stores connect
to elected master store and start receiving journal updates and
synchronize their data files with the master.
On Thu, Oct 30, 2014 at 5:20 AM, khandelwalanuj
wrote:
> Hi,
>
> I have gone through
> http://activemq.apache.org/repl
Hi,
Can I ask what is the current timeplan for ActiveMQ 5?
Will there be continued updates to version 5 or has development switched to
version 6?
Regards,
David
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-update-timeplan-tp4686812.html
Sent from the Acti
Tim,
Thanks for that, but I'm trying to get rid of the messages by fixing the issue
of the messages going outstanding, not changing the logging levels or turning
off the feature. :)
Anyone have a troubleshooting path or tuning recommendation, by chance?
Tim Bain wrote:
Well, you could get r
Well, you could get rid of those messages by choosing not to delete
inactive destinations (documentation:
http://activemq.apache.org/delete-inactive-destinations.html).
Or you could tune Log4J to only show WARN level messages for that Logger
On Thu, Oct 30, 2014 at 10:01 AM, Lodgen, Brad
wro
What you're suggesting sounds like it would behave the same as if I use the
static: transport with two nested URIs, except that I'd have more
configuration boilerplate since I'd have an additional networkConnector on
which I'd have to set all of my config options. Do I get something from
using the
I'm still learning tunables in activemq. Right now, I'm trying to tune and
troubleshoot my environment to get rid of the numerous activemq.log entries
showing "Inactive for longer than X ms - removing ...". I currently have the
timeout set to 6ms, but the messages I'm sending normally respon
you may be able to achieve what you want with two network connectors. one
to the primary and one to the backup. When both are alive and you use
decreaseNetworkConsumerPriority and priority dispatch, messages should take
the shortest path (priority decreases with number of hops).
On 24 October 2014
Hi all,
we encounter the following somewhat strange behaviour with ActiveMQ 5.8.0. I
had no luck finding anything similar on the net about it though.
We run an embedded broker with multiple queues. Non-persistent messages are
put into Queue 1 by the clients. Consumers pull them from there (prefet
Hi,
I have gone through
http://activemq.apache.org/replicated-leveldb-store.html.
What does zookeeper do other than election of master from ActiveMQ brokers ?
Who takes care of replicating data from master broker to other slaves ?
Thanks,
Anuj
--
View this message in context:
http://activ
12 matches
Mail list logo