Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of rajdavies@gmail.com
 designates 209.85.212.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=jlDGJqFXUsttmoufmezh/4+Vaw7cIIiKXSKzlmjTP2MyQV38tyWuILVvYfdh5IcdlF
         HlgrG3ug8QLU31M4pJRwiC8EIS769m+DqfdcSMSjxOT2LTYD64K53KViZIz4k+V+JiRR
         7FflByyTI1JQj2D7DXIAt7nbN/SWzTombmb2g=
Message-Id: <F82AF9B8-C8B2-416C-82AC-01FC32FE6F2D@gmail.com>
From: Rob Davies <rajdavies@gmail.com>
To: users@activemq.apache.org
In-Reply-To: <27664135.post@talk.nabble.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Stuck messages - Dispatch issues
Date: Sat, 20 Feb 2010 18:13:02 +0000
References: <20467949.post@talk.nabble.com> <27664135.post@talk.nabble.com>

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/