From users-return-6132-apmail-qpid-users-archive=qpid.apache.org@qpid.apache.org Fri Apr 13 07:56:18 2012 Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-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 C878995B9 for ; Fri, 13 Apr 2012 07:56:18 +0000 (UTC) Received: (qmail 40354 invoked by uid 500); 13 Apr 2012 07:56:18 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 40327 invoked by uid 500); 13 Apr 2012 07:56:18 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 40301 invoked by uid 99); 13 Apr 2012 07:56:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Apr 2012 07:56:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.161.170] (HELO mail-gx0-f170.google.com) (209.85.161.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Apr 2012 07:56:08 +0000 Received: by ggmb2 with SMTP id b2so1487626ggm.15 for ; Fri, 13 Apr 2012 00:55:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=EKvzdExsyUC5b2xIX2jyoBF2u0B7BcUFEcXJ0P/HCSM=; b=GZA6oVEsafmaspejFX6KT+6hMEEjHBR5hAbHxCvbrgThL1cg3Xwp5LSNTSUsgmli1o Pf0sZ7LYTIqPQp3/tcyUgnk4SJIClf5hPc6+4+8Tq+PrWRjDZn69Bk1MAKssIZJnad6n wAp/3mFaLz1MKjx6MVgm1rtsJ/od/YKuPKd/Y2d1e5Ex7IhvzUtzke4VvmGdvVSSeHax XSwLd0rgUh8A+earUm9L+RRsNe/AkxNHy1p84DtizI4XTXv3Ualm5ugec/i718eaTvHT QZTIMchQDGQy46dJuN1dNgJou3eGNbeSWLuBSLNZvQ/o4HDyLTS53JC7sVkZyFQdpUMo ogYg== MIME-Version: 1.0 Received: by 10.236.200.228 with SMTP id z64mr810165yhn.10.1334303747884; Fri, 13 Apr 2012 00:55:47 -0700 (PDT) Received: by 10.236.70.2 with HTTP; Fri, 13 Apr 2012 00:55:47 -0700 (PDT) X-Originating-IP: [193.29.76.37] In-Reply-To: References: <532c36b6-a6c4-4905-b3fd-d39ec31839a4@zmail02.collab.prod.int.phx2.redhat.com> <4f88a586-0276-4fdc-a191-416b58d00c81@zmail02.collab.prod.int.phx2.redhat.com> Date: Fri, 13 Apr 2012 09:55:47 +0200 Message-ID: Subject: Re: Selective message acknowledgment in Java client (and C++ broker)? From: Jakub Scholz To: users@qpid.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlZVK8YD5arfdFbWpYvZO9B0j1Rjslj24c3NZqCxX+K/lJCfj1be/jGK9aZUOrgFgMtnYv8 Hi Rajith, I was playing with the JMS selectors last week. While they do work and really select the messages based on the filter, it seemed to me that it switched off the acknowledgments completely. The Java application was getting only the selected messages, but I was unable to acknowledge them and they stayed in the queues. This may be OK in some situations, but in my case I wanted to get the messages really acknowledged and removed from the queues on the broker. Then I considered to try the same trick as Pavel did - read all messages and filter them manually. But unlike in the C++ API, I didn't found any methods for acknowledging specific message as well as for releasing or rejecting a message. Regards Jakub On Fri, Apr 13, 2012 at 07:43, Rajith Attapattu wrote: > (Note for C++ broker we do client side selectors, which does exactly what > you have described). --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org