Bumping the logging level is key to this; even if you succeed in finding
data files that demonstrate what happened, without the more detailed
logging it may be impossible to tell *why* it happened. If you get a large
enough disk attached to the machine to hold months of logs, that's great,
just mak
Is there anything in the broker's logs when this happens? I believe the log
content you quoted was from the client, not the broker, and I wasn't sure
if what you wrote meant that there was nothing in the broker's logs, so I
want to make sure.
Can you reproduce the problem in a non-production envir
Background : We use AMQ to exchange MQTT non-persistent messages between our
server components and clients (Android/iOS devices). About 100-200
messages/second get exchanged during peak hours.
This is our MQTT transport connector configuration :
When there are more than 1 MQTT connections (a
Hi Tim,
Thx for your answer.
Regards
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
It is possible that there is a bug in the ack compaction feature, but if so
it only shows itself in
some very special cases. I have tried stressing it, but to no avail. In all
my tests the broker
does the right thing.
There are no cron jobs deleting any files in this system. The broker thinks
that
