You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Diego Castorina <di...@func.nl> on 2009/12/15 11:50:36 UTC
Re: Q Consumers stop receiving messages
We are experiencing similar problems.
We are informed by the mbean queueSize property that around 5000 messages
are still in the queue.
This is the configuration of our broker:
<amq:broker brokerName="mdms-broker" start="true"
dataDirectory="${importer.jms.directory}" >
<amq:destinationPolicy>
<amq:policyMap>
<amq:policyEntries>
<amq:policyEntry queue="*" producerFlowControl="false">
<amq:dispatchPolicy>
<amq:strictOrderDispatchPolicy/>
</amq:dispatchPolicy>
<amq:subscriptionRecoveryPolicy>
<amq:lastImageSubscriptionRecoveryPolicy/>
</amq:subscriptionRecoveryPolicy>
</amq:policyEntry>
</amq:policyEntries>
</amq:policyMap>
</amq:destinationPolicy>
<amq:transportConnectors>
<amq:transportConnector
uri="${importer.jms.transportConnector.uri}"></amq:transportConnector>
</amq:transportConnectors>
</amq:broker>
Is there any workaround for timeout issue?
Thanks for any tip
--
View this message in context: http://old.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p26792856.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Q Consumers stop receiving messages
Posted by Diego Castorina <di...@func.nl>.
The test with prefetchLimit set to 1 has just completed successfully!!!
Just one last question.Suppose that prefetchLimit is 1 and one message is
sent to a queue that at the moment is not being used by the
DefaultMessageListenerContainer, than I would still have one message not
being processed until a new message is sent to the queue, right?
Would it be a solution to set the cacheConsumers property of the
DefaultMessageListenerContainer equal to false, since creating a new
consumer should not be a really expensive operation?
Thanks a lot for your help!
rajdavies wrote:
>
> 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/
>
>
>
>
>
>
>
--
View this message in context: http://old.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p26812140.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Q Consumers stop receiving messages
Posted by Rob Davies <ra...@gmail.com>.
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/
Re: Q Consumers stop receiving messages
Posted by Diego Castorina <di...@func.nl>.
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.
Re: Q Consumers stop receiving messages
Posted by Diego Castorina <di...@func.nl>.
Yes, it is.
rajdavies wrote:
>
> Is this version 5.3 ?
> On 15 Dec 2009, at 10:50, Diego Castorina wrote:
>
>>
>> We are experiencing similar problems.
>> We are informed by the mbean queueSize property that around 5000
>> messages
>> are still in the queue.
>> This is the configuration of our broker:
>>
>> <amq:broker brokerName="mdms-broker" start="true"
>> dataDirectory="${importer.jms.directory}" >
>> <amq:destinationPolicy>
>> <amq:policyMap>
>> <amq:policyEntries>
>> <amq:policyEntry queue="*" producerFlowControl="false">
>> <amq:dispatchPolicy>
>> <amq:strictOrderDispatchPolicy/>
>> </amq:dispatchPolicy>
>> <amq:subscriptionRecoveryPolicy>
>> <amq:lastImageSubscriptionRecoveryPolicy/>
>> </amq:subscriptionRecoveryPolicy>
>> </amq:policyEntry>
>> </amq:policyEntries>
>> </amq:policyMap>
>> </amq:destinationPolicy>
>> <amq:transportConnectors>
>> <amq:transportConnector
>> uri="${importer.jms.transportConnector.uri}"></amq:transportConnector>
>> </amq:transportConnectors>
>> </amq:broker>
>>
>> Is there any workaround for timeout issue?
>>
>> Thanks for any tip
>> --
>> View this message in context:
>> http://old.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p26792856.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/
>
>
>
>
>
>
>
--
View this message in context: http://old.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p26794952.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Q Consumers stop receiving messages
Posted by Rob Davies <ra...@gmail.com>.
Is this version 5.3 ?
On 15 Dec 2009, at 10:50, Diego Castorina wrote:
>
> We are experiencing similar problems.
> We are informed by the mbean queueSize property that around 5000
> messages
> are still in the queue.
> This is the configuration of our broker:
>
> <amq:broker brokerName="mdms-broker" start="true"
> dataDirectory="${importer.jms.directory}" >
> <amq:destinationPolicy>
> <amq:policyMap>
> <amq:policyEntries>
> <amq:policyEntry queue="*" producerFlowControl="false">
> <amq:dispatchPolicy>
> <amq:strictOrderDispatchPolicy/>
> </amq:dispatchPolicy>
> <amq:subscriptionRecoveryPolicy>
> <amq:lastImageSubscriptionRecoveryPolicy/>
> </amq:subscriptionRecoveryPolicy>
> </amq:policyEntry>
> </amq:policyEntries>
> </amq:policyMap>
> </amq:destinationPolicy>
> <amq:transportConnectors>
> <amq:transportConnector
> uri="${importer.jms.transportConnector.uri}"></amq:transportConnector>
> </amq:transportConnectors>
> </amq:broker>
>
> Is there any workaround for timeout issue?
>
> Thanks for any tip
> --
> View this message in context: http://old.nabble.com/Q-Consumers-stop-receiving-messages-tp21438163p26792856.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/