> On 4 Nov 2016, at 18:12, mlange wrote:
>
> Could it be a (or more) messages staying on a queue, causing the logs not to
> be cleared?
No, all messages are consumed and nothing is stored on the server.
We recived two tips from otherside this list:
* Try with the latest JDK
* Disable NIO.
So
We have two brokers configured in a network of brokers.
Both stores the messages on local disk using KahaDB.
And they both run ActiveMQ-5.13.4 in java 8u45.
Clients are allowed to connect through openwires and amqps:
We have about 10 queues
Thanks for your reply.
> On 27 Sep 2016, at 14:59, Tim Bain wrote:
>
> Do the stats you see in JConsole line up with KahaDBJournalReader (what's
> that?), or with the web console? And do you see an open XA transaction in
> JConsole, like Steve did?
No traces of XA transactions.
> I'd guess th
I will hijack this thread since I have almost the same problem. Log
files the filling up disk and TRACE telling me:
"not removing data file: XXX as contained ack(s) refer to
referenced file: [XXX]"
Running ActiveMQ 5.13.4.
I hacked'n'slashed KahaDBJournalReader (would be great if the source
code c
> On 13 Jul 2016, at 14:41, Tim Bain wrote:
>
> This is new, so please submit a bug in JIRA. Please include as much
> information as you can about your configuration and how your broker is
> being used; because you're seeing problems while no one else is and this
> appears to be code everyone s
Hi!
We have two brokers esb-test-mq01 and esb-test-mq02 configured in a
network of brokers. Each broker has configuration like this:
Both brokers running ActiveMQ 5.13.0, Java 1.8.0_45 and Ubuntu 14.04
(3.13.0-87-generic x86_64).
Sometimes (we havn't found any patterns for when it occurs) one
first and include all the content of the generic case
>> along with the things that are specific.
>>
>> Tim
>> On Jun 10, 2016 2:54 AM, "Johan Carlquist" wrote:
>>
>> Hi!
>>
>> Our config:
>> =
>>
>> [...]
Hi!
Our config:
=
[...]
[...]
=
So we have some queues; queue1, queue2 and so on. They all match the
first wildcard entry in the configuration and allows messages to jump
between our network of brokers even if they already been tra