It might be worth turning off producer flow control - see
http://cwiki.apache.org/ACTIVEMQ/producer-flow-control.html
On 9 Feb 2010, at 02:04, hwl wrote:
Found a thread in the forum on similar issue that links to
http://cwiki.apache.org/ACTIVEMQ/my-producer-blocks.html.
We tried, and do not observe the blocking issue so far. However, the
performance dropped, with the average response time now at about
600ms. We
set the usageManager limit to 128MB and tried 512MB as well. Are
there some
other configs that we can tune further?
Thanks!
hwl wrote:
Our application previously ran on activemq 4.1.2 and was able to
achieve <
500ms response time in average. However, some locking issue was
observed
(WAITING on
edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar)
and we upgraded the activemq component to 5.3.0. The locking issue
does
not occur so far, but the performance drops to >2 second on average
response time which breaches the performance critieria.
Any idea what could introduce such significant overhead and any way
to
tune it?
Our messaging service is non-persistent and activemq has been
configured
accordingly.
thanks!
- Wanling
--
View this message in context:
http://old.nabble.com/activemq-5.3-slower-than-4.1.2--tp27486527p27509403.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/
