I'd try 5.3 - there's been a lot of issues resolved since 5.2 - its
possible you've hit an resolved issue
On 3 Jan 2010, at 18:11, softsky wrote:
Hello guys.
My situation is:
Using AMQ 5.2.0. Have 1 consumer and 10 producers. Producers sends
thousands
of messages (in total) to some queue from different boxes. Consumer
consumes
them with some speed. Producers produce more messages per some time,
then
consumer can handle. If I run same consumer and up to 3 producers -
everything works fine for weeks. Queue is always empty as consumer
picks
messages up as fast as 3 producers produce them. However, if I run
more
producers - AMQ becomes slave. The more messages sits in the queue -
the
slower AMQ is. I've tried different combinations of persistence
adapter
configuration.
In my case it's:
syncOnWrite="false"
maxFileLength="32mb"
indexBinSize="16384"
indexPageSize="128kb"
But this seems does not help much. I'm almost assured there's no
side-effect
on OS-level (e.g. many files opened, too high swap usage -
nothing). CPU on
the box where consumer (and AMQ server) sits is almost IDLE. Looks
like AMQ
just sends too few messages to consumer for some reason (get slower
and
slower sending messages). One more detail - AMQ is running as embedded
inside another container (so both AMQ and consumer code works inside
same
JVM. Consumer use Apache Camel to process messages).
--
View this message in context:
http://old.nabble.com/ActiveMQ-becomes-slow-for-consumer-tp27002970p27002970.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/