Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 04E3A200B36 for ; Wed, 6 Jul 2016 18:42:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0397C160A64; Wed, 6 Jul 2016 16:42:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4AADE160A55 for ; Wed, 6 Jul 2016 18:42:24 +0200 (CEST) Received: (qmail 11259 invoked by uid 500); 6 Jul 2016 16:42:23 -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 11248 invoked by uid 99); 6 Jul 2016 16:42:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jul 2016 16:42:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A00E7CA6F2 for ; Wed, 6 Jul 2016 16:42:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.309 X-Spam-Level: X-Spam-Status: No, score=-6.309 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id w5_daSYxUZ1f for ; Wed, 6 Jul 2016 16:42:18 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E025B5FCCF for ; Wed, 6 Jul 2016 16:42:17 +0000 (UTC) Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 01BB4C05B1CD for ; Wed, 6 Jul 2016 16:42:17 +0000 (UTC) Received: from localhost.localdomain (ovpn-116-24.phx2.redhat.com [10.3.116.24]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u66GgGNb009676 for ; Wed, 6 Jul 2016 12:42:16 -0400 Subject: Re: Service Bus: unreceived messages stay locked (peek-and-lock) To: users@qpid.apache.org References: From: Gordon Sim Organization: Red Hat UK Ltd, Registered in England and Wales under Company Registration No. 3798903, Directors: Michael Cunningham, Michael O'Neill, Eric Shander Message-ID: <13586ea8-ddcc-4e63-d3c7-932b92631dad@redhat.com> Date: Wed, 6 Jul 2016 17:42:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Wed, 06 Jul 2016 16:42:17 +0000 (UTC) archived-at: Wed, 06 Jul 2016 16:42:25 -0000 On 06/07/16 17:14, Dale Green wrote: > I have an update on this issue. > > According to Microsoft, state=Released is supported and now I can confirm > that this is true. If the message is released during the lifetime of the > consumer (before Detach), the same message is immediately unlocked and is > available for the same consumer or others depending on the credit. > > However, what happens with Qpid JMS is that messageConsumer.close() first > sends a Detach frame and after that the Disposition frames if any. Is this > correct from protocol point of view, as Service Bus seems to ignore such > dispositions? The spec says: The disposition performative MAY refer to deliveries on links that are no longer attached. As long as the links have not been closed or detached with an error then the deliveries are still “live” and the updated state MUST be applied. If the Detach sent by the client has closed=true, then I would think that the deliveries associated with that link are implicitly ended. If this is the case, then the client has a bug. (If the closed flag was false, then I would think it would depend on the expiry-policy for the link's source). > Is there any way to set the credit to 0, send the Dispositions, and then > Detach? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org