It's indeed sequential, and I bet this can be improved. Open a jira and we
can track it.
On Mon, May 20, 2013 at 1:48 PM, Oleg Dulin wrote:
> Dear Colleagues:
>
> We have about 1500 queues on the broker. Some queues are consumed in a
> "batch" fashion. So the journal gets fragmented and become
Dear Colleagues:
We have about 1500 queues on the broker. Some queues are consumed in a
"batch" fashion. So the journal gets fragmented and becomes quite
large. To optimize disk usage, I've done the following:
Hello,
Thanks for your reply. I added my debugging info to the jira issue. It
would be great to get this issue fixed soon.
br,
ilia
2013/5/18 Christian Posta
> Thanks for the debugging info!
> Looks like this issue has been raised:
> https://issues.apache.org/jira/browse/AMQ-4487
>
> When one
You can start by taking a look at
http://activemq.apache.org/advisory-message.html
Advisory messages fire when interesting events happen in the broker, and
listening to the topic for consumers might get you what you're looking for.
On Sun, May 19, 2013 at 7:32 PM, ννΈμ(Hoyeong Heo) <
hoyeong@h
