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 E8C99200CF9 for ; Sun, 17 Sep 2017 14:41:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E73531609D8; Sun, 17 Sep 2017 12:41:06 +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 38E271609BF for ; Sun, 17 Sep 2017 14:41:06 +0200 (CEST) Received: (qmail 37260 invoked by uid 500); 17 Sep 2017 12:41:05 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 37251 invoked by uid 99); 17 Sep 2017 12:41:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Sep 2017 12:41:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D0698183BA3 for ; Sun, 17 Sep 2017 12:41:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -97.888 X-Spam-Level: X-Spam-Status: No, score=-97.888 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URI_HEX=1.313, URI_TRY_3LD=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Birpag2SNfRE for ; Sun, 17 Sep 2017 12:41:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DF7995FDA3 for ; Sun, 17 Sep 2017 12:41:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 62929E010F for ; Sun, 17 Sep 2017 12:41:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1314A25382 for ; Sun, 17 Sep 2017 12:41:00 +0000 (UTC) Date: Sun, 17 Sep 2017 12:41:00 +0000 (UTC) From: "Yogesh Rao (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-6534) QueueBrowser can view messages being processed by consumers which are not yet acknowledged MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 17 Sep 2017 12:41:07 -0000 [ https://issues.apache.org/jira/browse/AMQ-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169280#comment-16169280 ] Yogesh Rao commented on AMQ-6534: --------------------------------- Hello [~gtully], Apologies didnt have much time for this.. I was looking into JIRA 5274 mentioned by you and also looked at the commit. This could be my lack in understanding of ActiveMQ codebase but i couldn't bridge the fix done with the one needed for this. > QueueBrowser can view messages being processed by consumers which are not yet acknowledged > ------------------------------------------------------------------------------------------ > > Key: AMQ-6534 > URL: https://issues.apache.org/jira/browse/AMQ-6534 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.14.1 > Reporter: Yogesh Rao > > ActiveMQ's Queue Browser API returns messages list that includes the ones which currently getting processed by a consumer (not sent the acknowledgment). I have seen this behaviour in ActiveMQ 5.13.3 and 5.14.1 > To replicate this issue following needs to be done. > 1. Publish 3 messages to queue Test > 2. In a stand alone code have a message listener which goes to sleep call of onMessage() (sleep for 10 mins) (Session is transacted false and Auto Acknowledge) > 3. In a different Stand alone code have a queue browser code with no selector specified. > We can see that QueueBrowser returns all the three messages instead of 2. > This behaviour differ from how Weblogic JMS, HornetQ and Apache Artemis work. > I am not sure if the above behaviour is intended. However it would be a great if ActiveMQ provides a way for QueueBrowsers to not see unacknowledged messages. > Disscussion on ActiveMQ Dev Forum :- http://activemq.2283324.n4.nabble.com/ActiveMQ-5-14-1-QueueBrowser-can-view-messages-being-processed-by-consumers-which-are-not-yet-unacknd-td4719662.html > -- This message was sent by Atlassian JIRA (v6.4.14#64029)