Sorry for the delay getting back to you.
I'm not clear what delay error messages you're referring to; if you're
still having problems related to them, can you include a sample to help
clarify what you mean?
I got the 70GB by multiplying your 70% JVM percentage by your 100GB store
limit instead of
On 14-12-08 08:57 PM, Tim Bain wrote:
The log line tells you how you're doing against two different limits: the
per-destination limit and the entire-broker limit. The per-destination
limit is first, and the log line says you're using 0% of what you've
allocated per destination, so you're right t
The log line tells you how you're doing against two different limits: the
per-destination limit and the entire-broker limit. The per-destination
limit is first, and the log line says you're using 0% of what you've
allocated per destination, so you're right that you're fine there. The
full-broker
Using ActiveMQ 5.9.1
Our setup: A Spring/JMS producer places many (sometimes quite large)
messages on one queue (hf.request), which are being picked up by a PHP
Stomp client. PHP processes the data and sends a message to a second
queue (hf.response) to let it know how things went.
Occasional
