Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.216.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1320329912992-3986026.post@n4.nabble.com>
References: <1320321259371-2358923.post@n4.nabble.com>
	<1320321259363-3985367.post@n4.nabble.com>
	<CAH+vQmN6mkh=F6C0rSqZs1xJEgBve8uCyYtEjj4h_kJrzx8b4g@mail.gmail.com>
	<1320329912992-3986026.post@n4.nabble.com>
Date: Thu, 3 Nov 2011 14:21:53 +0000
Message-ID: 
 <CAH+vQmPzLph7xFFms=nQdThnOyVaWOoyHhJQU0Gm5LGTkNSwxQ@mail.gmail.com>
Subject: Re: Redelivery sticks to and blocks a consumer thread
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

sorry, not sure about NMS. Keeping message order is the default so I
think NMS would need a similar enhancement to support out of order
delivery.

On 3 November 2011 14:18, Ishitori <Ishitori@bk.ru> wrote:
> Hi, Gary.
>
> Thanks for the answer. I forgot to mention that I am using NMS. Does it make
> the difference? I mean, that you gave the link to ActiveMQ client code,
> right? Is there something like that for NMS?
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Redelivery-sticks-to-and-blocks-a-consumer-thread-tp2358923p3986026.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
http://fusesource.com
http://blog.garytully.com