Re: Out of Memory on 5.3

s always < 2. > Can you 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 > >> >> the test scene: after accumulate a

Re: Out of Memory on 5.3

> Can you 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 > >> >> the test scene: after accumulate a large of message

Re: Out of Memory on 5.3

gt; destination keeps responding. > > 2009/11/12 afei > >> >> 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 slo

Re: Out of Memory on 5.3

t; resolving https://issues.apache.org/activemq/browse/AMQ-2481 > > 2009/11/10 afei : >> >> in org.apache.activemq.broker.region ,why so many invoke asyncWakeup(), >> what is the method:iterate() doing? >> >> >> afei wrote: >>> >>> in ad

Re: Out of Memory on 5.3

pache.org/activemq/browse/AMQ-2481 > > 2009/11/10 afei : >> >> 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. >

Re: Out of Memory on 5.3

pache.org/activemq/browse/AMQ-2481 > > 2009/11/10 afei : >> >> 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. >

Re: Out of Memory on 5.3

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 &g

Re: Out of Memory on 5.3

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 : >> >> >> when a large of messages in queue,and no

Re: Out of Memory on 5.3

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 : >> >> >> when a large of messages in queue,and no

Re: Out of Memory on 5.3

;> So we turned off stomp+nio and went back to plain old stomp and so far >> it's >> working fine. New(IO) isn't always better, I guess :-) >> >> Seems like maybe it's this issue -> >> https://issues.apache.org/activemq/browse/AMQ-2440 >> >

Re: Out of Memory on 5.3

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