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 gcjau-user-2@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: users@activemq.apache.org
From: Aleksandar Ivanisevic <aleksandar@ivanisevic.de>
Subject: Re: Queue does not drain completely.
Date: Mon, 13 Jul 2009 13:18:02 +0200
Organization: Individual
Lines: 74
Message-ID: <m3d4846dcl.fsf@alex.2e-systems.com>
References: <24296039.post@talk.nabble.com> <24302432.post@talk.nabble.com>
 <24306748.post@talk.nabble.com> <24308342.post@talk.nabble.com>
 <24308386.post@talk.nabble.com> <24308863.post@talk.nabble.com>
 <24427058.post@talk.nabble.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Original-Sender: aleksandar@ivanisevic.de
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
Cancel-Lock: sha1:EmasqqwOFwhDX3AdYZBRpUKdIIY=
Sender: news <news@ger.gmane.org>

RakeshRay <Rakesh.Ray@Proquest.com> writes:

> Thanks for the suggestions, I tried, but does not help.
> It could be the problem with the Stomp protocol!.
> Anyone using Stomp to Connect to use Active MQ?

I'm using STOMP with perl Net::Stomp and it is working reasonably good
for simple use. 5.3.SNAPSHOT is buggy once you go to more advanced
features (i.e. transactions). see i.e. AMQ-2280

BTW, I always use can_read before the actual read.

> mjustin wrote:
>> 
>> If it depends on message number / message size, maybe the broker needs
>> more buffer space, you can try increasing the memoryLimit in the
>> activemq.xml file. It helped with a similar problem where the producer
>> stopped after a small number of messages until I increased the value to
>> 50mb.
>> 
>>         <!-- Destination specific policies using destination names or
>> wildcards -->
>>         <destinationPolicy>
>>             <policyMap>
>>                 <policyEntries>
>>                     <policyEntry queue=">" memoryLimit="5mb"/>
>>                     <policyEntry topic=">" memoryLimit="5mb">
>>                     </policyEntry>
>>                 </policyEntries>
>>             </policyMap>
>>         </destinationPolicy>
>> 
>> 
>> RakeshRay wrote:
>>> 
>>> I tried with 1000 messsages or 800 byte/each, that is small enough.
>>> I removed can_read before read_frame and seems behaving okay. Reading
>>> more to figure out if can_read is really required in my case or not!
>>> Thanks for the other suggestions, though.
>>> 
>>> mjustin wrote:
>>>> 
>>>> I am using 5.2 and 5.3-Snapshot. Have you tried to test it with a
>>>> smaller number of messages, and without transactions? 
>>>> 
>>>> 
>>>> RakeshRay wrote:
>>>>> 
>>>>> 
>>>>> Hi, 
>>>>> We have written a wrapper around and internally it is using using
>>>>> timeout feature.
>>>>> What version of Active MQ are you using?
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
>
> -- 
> View this message in context: http://www.nabble.com/Queue-does-not-drain-completely.-tp24296039p24427058.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

-- 
Gle, svaka cast tebi i tvom poslu ali kaj nas moras svaki puta dojit sa 
tvojom placom i poslom itd. Pa svaki post koji postas prije ili kasnije 
pocinje aludirati na tvoje vrhunaravne izvore prihoda i materijalnih dobara. 
Daj se sredi malo. Mislim da na ama bas nikoga ne zanima koliko ti zaradujes 
i kako trosis svoje pare. Tomislav Kralj - hr.comp.programiranje.baze