Hi,
I have a set of network of brokers with the following configurations, i.e.
all resides on 4 different servers (ie different IP addresses)
Broker A (master)Broker B (master)
I strongly believe these MyEventQueue1 and MyEventQueue2 queues messages
are consumed successfully .
As indicated, there are many duplicates messages detected for the same queue
which resulted in DLQ. I deployed the broker DLQ plugin
(discardingDLQBrokerPlugin) to discard all the messages.
I
I managed to clear the journal logs on those queues mentioned.
The daily (earlier) journal logs file size is about 10GB.
The journal logs only get cleared when concurrentStoreAndDispatchQueues is
set to false.
However, my producer application ( runs another ActiveMQ server), active
"I wasn't aware of any reason that the logging config and debugging
techniques described on that page would not work properly with mKahaDB. Can
you please elaborate on the failure you referenced?"
- Added the log4j.properties with the following
Based on the link
https://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
I tried to setup the journal log to see which the reasons for the missing
logs. But failed -my setup is using mKahadb rather than Kahadb.
I only knows which queue that has lots of journal logs - in my
Hi,
I have broker that runs with increasing journal logs file with mKahadb store
for each destination.
One of the queue - journal logs are keep increasing overtime.
The strange part is that - everytime I restart activemq, these journal log
files get deleted.
To me, it looks like the
ots of duplicate message for MyEventQueue1 an MyEventQueue2
Question:
1. What is the possible causes for the frequent network bridge connection
drops, and how do I avoid duplicate queue messages at Broker B1 or B2 ?
Thanks
-TC
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi,
After creating the network of brokers, i.e. about 4 of them on the same
laptop.
I can start them without any problem.
Not sure what I have changed in between - not it doesnt start.
Here is error exception - any guides on how to troubleshoot more
Loading message broker from: