Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6F809E59F for ; Tue, 5 Feb 2013 16:17:51 +0000 (UTC) Received: (qmail 82878 invoked by uid 500); 5 Feb 2013 16:17:49 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 81849 invoked by uid 500); 5 Feb 2013 16:17:46 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 80457 invoked by uid 99); 5 Feb 2013 16:16:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 16:16:53 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com designates 209.85.223.181 as permitted sender) Received: from [209.85.223.181] (HELO mail-ie0-f181.google.com) (209.85.223.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 16:16:49 +0000 Received: by mail-ie0-f181.google.com with SMTP id 17so441062iea.12 for ; Tue, 05 Feb 2013 08:16:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=yArXysQNREuoJqql014BJtMUEnlpwyeZGGWwOhkexoc=; b=Bp5QwQXQXluD+qkwwEmiJk8/hBVqZZ7FQs9GRitZW9lWSMjrIjNe1Nwgl7ps1DAbGn DqQC5SNcEoeU9iwNTAMwLlUX2gRRJpWVAwD177DLqV+gieZn3Mis2fgQ8/f6kr3v3Teq sHb7aFhj83D0Usmfh0qc4NXvMX2rUVDPUAGq8j4VsnJjyvSqIB4V8Liyja5OX0M/qghS uHSq31ehjgC5f3PtuTr1+0uG8iZkgbfXKOQ/1m+BVt7f/neoP/BAoqObii4zP3HfGRzK tNKG2QxBvlevOXuL2AlJfZhwZPQIsbzqCc+/EtNQ0tIcwsrtBAkth8CuekrlkUadmbVt 21CQ== MIME-Version: 1.0 X-Received: by 10.50.179.100 with SMTP id df4mr14350265igc.60.1360080988274; Tue, 05 Feb 2013 08:16:28 -0800 (PST) Received: by 10.50.41.100 with HTTP; Tue, 5 Feb 2013 08:16:28 -0800 (PST) In-Reply-To: <1359749072332-4662656.post@n4.nabble.com> References: <1359578770983-4662468.post@n4.nabble.com> <1359614255087-4662500.post@n4.nabble.com> <1359749072332-4662656.post@n4.nabble.com> Date: Tue, 5 Feb 2013 09:16:28 -0700 Message-ID: Subject: Re: Does the ">" destination wildcard require at least one character preceding it? From: Christian Posta To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=14dae93405fd2c01c704d4fc886e X-Virus-Checked: Checked by ClamAV on apache.org --14dae93405fd2c01c704d4fc886e Content-Type: text/plain; charset=ISO-8859-1 So I can recreate a priority message failure in our unit tests similar to what you're describing. It may be different though, so I'll have to look closer. How many messages are you using to test to recreate your scenario? over 200 by chance? On Fri, Feb 1, 2013 at 1:04 PM, Steve.V. wrote: > Well, my tester has encountered more prioritized message queue test > failures > even though she removed those prefetch=0 policies from the activemq.xml > config file, and the failures are resolved if she uses a queue name when > specifying the prioritizedMessages="true" policy, instead of attempting to > use simply ">" for all queues. > > Btw, my REST client is very unhappy when I set consumer.prefetchSize=0 in > "webapps/demo/WEB-INF/web.xml" via: > > > destinationOptions > consumer.prefetchSize=0 > > > Is that supported for REST API clients? > > > > ----- > Stephen Vincent > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Does-the-destination-wildcard-require-at-least-one-character-preceding-it-tp4662468p4662656.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta --14dae93405fd2c01c704d4fc886e--