Hi Tim,
thank you for your explanation. I will do the following things:
- increasing the store usage limit
- configure mKahaDb with several folders for several projects or use cases
It seems that AMQ in version 5.14.4 can handle log files much better than in
version 5.13.1 *if I separate the kah
On the other hand I could configure with mKahaDb several kahadb folders for
specific queues. But the configuration is not changeable at runtime and
restarting of the broker if we detect problems is not an option.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/general-pr
Hi Tim,
ok I have tested it out.
I'am using AMQ 5.14.4 for testing:
I have configured the following:
My test appliacation creates one pending message and afterwards one message
for every 10 milliseconds which will be consumed. Unfortunately the kahadb
folder still increases with log files.
Ac
Hi Tim,
increasing the store limit is a way but after 2 hours our kahadb folder
reaches 1GB. For me it seems that this is too much because sometimes we have
just 1 pending message and 1GB of log files.
Maybe there is an other way? :-)
--
View this message in context:
http://activemq.2283324.
Hi Tim,
an expiration value would result in lost messages if they are not processed
before the expiration, right?
But some times messages are not processed over the weekend because of a down
time of the consuming system. In such a case we did not want lost pending
messages.
--
View this messag
Hi all,
we are using the ActiveMQ-Broker in version 5.13.1 for several projects and
it works fine. But there is one thing what I haven't understand correctly.
If we have a queue with pending messages the amount of log files in the
kahadb data folder grows permanantly. After some time when the fol
