activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Elliot Barlas <elliotbar...@gmail.com>
Subject Re: Stuck messages - Dispatch issues
Date Sat, 20 Feb 2010 19:49:15 GMT

Yes.  I am using spring 3.0, but not for JMS.  I manage my own connections,
sessions, producers, and consumers.  I have tried reproducing the issue in a
test case, but I cannot.  It only occurs in my application, when I have
roughly 20 or more concurrent consumers, each associated with a different
session.  I am using the VM transport exclusively, as all communication
takes place with an embedded AMQ message broker.  

Thanks,
Elliot



rajdavies wrote:
> 
> Do you still get problems if not using Spring ?
> 
> On 20 Feb 2010, at 07:12, Elliot Barlas wrote:
> 
>>
>> Was this issue ever resolved?  I am seeing this as well with a large  
>> number
>> of concurrent consumers.  Same symptoms.  Lost messages until broker
>> restart.
>>
>> Thanks,
>> Elliot
>>
>>
>>
>> chrajanirao wrote:
>>>
>>> We are seeing issues with ActiveMQ 5.1 and 5.2 RC2 with message
>>> dispatching from queues. It is easily reproducible even using the  
>>> out of
>>> the box activemq configuration.
>>>
>>> Send messages to the a queue (QueueA) using multiple threads (10 or  
>>> 20
>>> thread in a loop of 10) using JMeter or your custom code. Have the
>>> consumer setup using spring DMLC (DefaultMessageListenerContainer)  
>>> or with
>>> regular JMS API sync or async consumption with multiple consumers.
>>> Consumer part can be configured using Camel to consumer from QueueA  
>>> and
>>> put the messages in QueueB within ActiveMQ configuration as well.
>>>
>>> After receiving some messages (the number is different each time),  
>>> the
>>> consumers stop receiving any messages even though there are some  
>>> left on
>>> the queue. Basically, the broker don't dispatch the messages  and  
>>> they are
>>> stuck until restart of the broker. Any new messages sent to the queue
>>> after this are sometimes dispatched and other times they are stuck  
>>> too.
>>>
>>> This certainly seems like a major bug in the dispatch mechanism. I  
>>> have
>>> found below posts that state the exact problem.
>>>
>>> http://www.nabble.com/Pending-Messages-are-shown-in-ActiveMQ-td20241332.html
>>>
>>> http://www.nabble.com/Consumer-Listener-stop-receving-message-until-ActiveMQ-restart-td20355247.html
>>>
>>> This is a very basic use case and I wonder how the version 5.1 is
>>> currently used in production, if anyone is using at all.
>>>
>>> We tried with prefetch limit as 1, asyncDispatch as true and false,
>>> session transacted as true and false. In all cases, the dispatch  
>>> problem
>>> still exists starting after 100 messages until 1000 messages.
>>>
>>> I hope any of the active commiters looks into this issue seriously.  
>>> Would
>>> really appreciate the help.
>>>
>>> Thanks,
>>> Rajani.
>>>
>>
>> -- 
>> View this message in context:
>> http://old.nabble.com/Stuck-messages---Dispatch-issues-tp20467949p27664135.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/Stuck-messages---Dispatch-issues-tp20467949p27669784.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message