Re: ActiveMQ refusing to send messages to my clients.

Hi Kevin, Knowing how the clients are consuming messages could help, i.e. whether it’s transactional or not, whether MessageConsumers are being reused/pooled, etc. As a long shot, I’d try lowering the prefetch limit client side. I’ve had to do this occasionally to work around inefficient Camel

Re: Several hundred messages occupies almost 30G storage

Hi, Two suggestions for you: 1. Try decreasing the logSize parameter for LevelDB. You’ve have a greater number of smaller log files, and a greater chance of each log file being garbage-collected. 2. With KahaDB, it’s possible to configure multiple KahaDB stores, and to put your dead-letter typ

Re: High CPU load with network connector, failover transport

By the way, I've noticed Lars has run into the same issue and posted via Nabble but it hasn't turned up on the mailing list yet: http://activemq.2283324.n4.nabble.com/Using-a-NetworkConnector-results-in-high-CPU-load-td4691627.html > On 20 Feb 2015, at 12:16 pm, Tim Robbins w

High CPU load with network connector, failover transport

Hi, We’ve noticed a regression in ActiveMQ 5.10.1 vs. 5.10.0 with a configuration similar to the following: Broker 1: networkConnector with static:(failover:(tcp://broker2 )?randomize=false&maxReconnectAttempts=0) Broker 2: networkConnector with static:(failover:(tcp://broker1 )?randomize=fal