OK, I nailed down the problem (and update the bug.) The default AMQ
Persistence store shipped with 5.2 is very slow. Clean out the data
directory wouldn't help. Switching over to Kaha works.
now, before the problem is fixed. I want to know what are the plus and minus
of using kaha store, comparin
Hi Gary,
we just made a new test which startet yesterday.
JVM settings of AMQ where 3 GB heap size.
We send about 800 msg / sec into the queue, the size was limited to 3 GB.
During that time sending messages to the queue got slower and slower. Even
after the queue was full and new messages have
Is there any way to configure maximumRedeliveries for a STOMP connection?
I ran tests against 5.2 and 4.1.1 and both redeliver the message
infinitely. This causes consumers to keep choking over and over again on
the same message unless the consumers implement their own maxRetries logic.
It looks
Test case written, bug filed.
https://issues.apache.org/activemq/browse/AMQ-2136
--
View this message in context:
http://www.nabble.com/Severe-performance-hit-upgrading-to-5.2.0-from-5.1-tp22016698p22141040.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The latest codes in the SVN still seems to receive from two receivers. Maybe
I miss something?
Anyway, I have written a test case which depends on nothing but AMQ. I was
using 5.1 and this bug shows up in 5.1; I tried running it in 5.2 for
several times, and it always works. [What prevents me fro
