do an svn up to validate.
thanks for the heads up on your fix. Think it is best not to limit the
pending wakeups to max page size as it may result in a hung destination.
2009/11/13 afei afei1...@126.com
the test scene: after accumulate a large of messages(about 5 millions) in
queue,begin
to validate.
thanks for the heads up on your fix. Think it is best not to limit the
pending wakeups to max page size as it may result in a hung destination.
2009/11/13 afei afei1...@126.com
the test scene: after accumulate a large of messages(about 5 millions) in
queue,begin to consume
.
2009/11/12 afei afei1...@126.com
when consuming a large of messages,the method:asyncWakeup() is invoked
crazily,so the executor
has a great deal of runnable that callback Queue.iterate(), but
Queue.iterate() is much slower than the increasing of runnable in the
executor. this result
://issues.apache.org/activemq/browse/AMQ-2481
2009/11/10 afei afei1...@126.com:
in org.apache.activemq.broker.region ,why so many invoke asyncWakeup(),
what is the method:iterate() doing?
afei wrote:
in addition,another problem of OOM.
Gary Tully wrote:
fyi: you can disable periodic message
in org.apache.activemq.broker.region ,why so many invoke asyncWakeup(),
what is the method:iterate() doing?
afei wrote:
in addition,another problem of OOM.
Gary Tully wrote:
fyi: you can disable periodic message expiry processing using a
destination policy entry that sets
/AMQ-2481
2009/11/10 afei afei1...@126.com:
in org.apache.activemq.broker.region ,why so many invoke asyncWakeup(),
what is the method:iterate() doing?
afei wrote:
in addition,another problem of OOM.
Gary Tully wrote:
fyi: you can disable periodic message expiry processing using
/AMQ-2481
2009/11/10 afei afei1...@126.com:
in org.apache.activemq.broker.region ,why so many invoke asyncWakeup(),
what is the method:iterate() doing?
afei wrote:
in addition,another problem of OOM.
Gary Tully wrote:
fyi: you can disable periodic message expiry processing using
i test r831258,the problem still exist
Gary Tully wrote:
fyi: you can disable periodic message expiry processing using a
destination policy entry that sets expireMessagesPeriod = 0
2009/11/9 afei afei1...@126.com:
when a large of messages in queue,and no consumer or the consumer
in addition,another problem of OOM.
Gary Tully wrote:
fyi: you can disable periodic message expiry processing using a
destination policy entry that sets expireMessagesPeriod = 0
2009/11/9 afei afei1...@126.com:
when a large of messages in queue,and no consumer or the consumer is very
i have same problem
http://www.nabble.com/file/p26093204/aa.jpg aa.jpg
themitchy wrote:
This is what we've done to tune so far:
- UseDedicatedTaskRunner=false
- flow control is off
- stomp transport uses transport.closeAsync=false
I agree that it is because of the
10 matches
Mail list logo