could be prefetch limit - the default is 1000 - would be worth trying
with 1
On 15 Dec 2009, at 13:54, Diego Castorina wrote:
I went a little bit further with my tests:
-the queue was containing 5219 messages and no one of them was
distributed
to any of the listeners (I set the maxConcurrentConsumers property
in the
DefaultMessageContainerListener of Spring to 20)
-I added 50 messages to the queue
-the first 50 message of the 5219 that were already in the queue
were sent
to the listeners
-the queue hangs again, still containing 5219 message and the last 50
messages add during the second step are probably at the bottom of
the queue
I repeated those steps several times, obtaining always the same
behavior.
it is like now the queue maintain the size it had as it started
hanging.
In my application I use
org.springframework.jms.connection.CachingConnectionFactory and set
the
sessionCacheSize to 100. Is it related to connection timeout as
reported in
http://jira.springframework.org/browse/SPR-5098? Has it something to
do with
prefetchLimit? Or is it more a combination of both ???
Please help :(
--
View this message in context:
http://old.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p26795148.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/
