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 BFCE2200CEB for ; Fri, 28 Jul 2017 21:10:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BE52916AD4F; Fri, 28 Jul 2017 19:10: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 1082116AD46 for ; Fri, 28 Jul 2017 21:10:05 +0200 (CEST) Received: (qmail 74851 invoked by uid 500); 28 Jul 2017 19:10: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 74840 invoked by uid 99); 28 Jul 2017 19:10:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jul 2017 19:10:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D2B301A1BEA for ; Fri, 28 Jul 2017 19:10:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id aKx3-nKLRmjv for ; Fri, 28 Jul 2017 19:10:04 +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 BE45061070 for ; Fri, 28 Jul 2017 19:10:03 +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 72FA4E0E40 for ; Fri, 28 Jul 2017 19:10:02 +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 17B7924DC4 for ; Fri, 28 Jul 2017 19:10:01 +0000 (UTC) Date: Fri, 28 Jul 2017 19:10:01 +0000 (UTC) From: "clebert suconic (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARTEMIS-1308) Client Acknowledge not performant MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 28 Jul 2017 19:10:06 -0000 [ https://issues.apache.org/jira/browse/ARTEMIS-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-1308: ------------------------------------- Affects Version/s: 2.2.0 Fix Version/s: 2.3.0 > Client Acknowledge not performant > --------------------------------- > > Key: ARTEMIS-1308 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1308 > Project: ActiveMQ Artemis > Issue Type: Bug > Affects Versions: 2.2.0 > Reporter: Michael Andre Pearce > Assignee: clebert suconic > Fix For: 2.3.0 > > > Artemis recommendation in docs is to use CLIENT_ACKNOWLEDGE instead of AUTO_ACKNOWLEDGE, on perf testing it seems this is not the case. > On checking code it seems the reason for this is because ActiveMQMessage acknowledge actually calls session.commit, causing a full session commit all the time. > On checking Core API, calling message.acknowledge it seems to behave as expected, as such believe this to be an issue in JMS api wrapper, that it should just be delegating to the ClientMessage.acknowledge method and this is the cause of the perf issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)