Sounds like the persistence store might be your bottleneck; how do you have
it configured?
On Jan 24, 2017 6:53 AM, "francong2000" wrote:
I have set up ActiveMQ 5.14.3 cluster (2 Brokers) with using Network
Connector. I tried to send 4,000 persistent message to a queue in 300
msg/sec rate. The
Christopher:
Thank you for your explanation!
Hope there would be other proper ways to shrink the index file in future
ActiveMQ releases.
Once we monitored that our broker is killed by system due to "out of
memory".
I know that meta cache in memory will be synced into index file at
checking
I'm wondering if these are coming about due to RESTful posts of new
messages...
If an HTTP client comes along and sends
POST /api/message?destination=queue://testqueue HTTP/1.1
is it going to try and use 'localhost' first and then fall back to the
actual broker name?
If so, should the client be
I have set up ActiveMQ 5.14.3 cluster (2 Brokers) with using Network
Connector. I tried to send 4,000 persistent message to a queue in 300
msg/sec rate. The Producer can send same rate (300m/s) with using
"useAsyncSend=true", however, consumer just can receive all messages in *40
msg/sec* rate.
The index grows based off the amount of data it tracks in the journal,
but doesn't shrink. This means if you had a lot of data in your
journal at some point (several gigabytes, etc) then the index would
have grown in size with enough page files to keep track of all of the
data. This is usually no
