So when I look at these, they correspond to the current defaults of 10 and
10M respectively:
10
10485760
I thought I was helping by setting the max size bytes. However, I've reset
this back to the default -1 value.
-1
No I did not change the page-size-bytes setting. I don't know wha
I would keep min large message size. And journal buffer size untouched.
And let them using the separated files.
You have tweak configurations to increase the size of what is large. But I
don’t think you bumped the config for page size. That could lead to
starvation’s and other things.
If u re
Your browse limitation was activated when you seated "Per Destination
Policies" in the broker settings
(http://activemq.apache.org/per-destination-policies.html). Please see
maxBrowsePageSize setting.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I'm doing some testing with the new v2.6.0 and I'm using
large messages. I'm seeing a lot of the following in my log. I expect paging
since my messages are over 3MB. Why is the paging size apparently increasing
only? The consumer is consuming (I'm continuing to run tests to re-verify
that) so I
My understanding is that, KahaDB rewrite the KAHA_SUBSCRIPTION_COMMAND to
latest journal file for ease of deletion the oldeset jorunal log,
when the durable subscriber has no pending message.
But, in the following case, "Durable Subscriber C and D" aren't rewritten
to latest journal despite th
Hi all, I use ActiveMQ 5.13.1 for MQTT.
It seems that ActivMQ writes some useless commands, when the durable
subscriber
is destroyed by Offline Timeout.
For example, the following situation:
- Topic a, b, c
- Durable Subscriber A, B, C
- "Durable Subscriber A" subscribe ONLY "Topic a"
-
