Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 31 Jan 2014 16:22:09 +0000 (UTC)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: <JIRA.12508059.1306158572492.18048.1391185329383@arcas>
In-Reply-To: <JIRA.12508059.1306158572492@arcas>
References: <JIRA.12508059.1306158572492@arcas>
Subject: [jira] [Updated] (APLO-20) Optimize session acked durable subs by
 using a shared durable queue.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/APLO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-20:
------------------------------

    Fix Version/s:     (was: 1.7)
                   1.8

> Optimize session acked durable subs by using a shared durable queue.
> --------------------------------------------------------------------
>
>                 Key: APLO-20
>                 URL: https://issues.apache.org/jira/browse/APLO-20
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>          Components: apollo-bdb, apollo-broker, apollo-leveldb
>            Reporter: Hiram Chirino
>             Fix For: 1.8
>
>
> Right now every durable sub gets assigned a new queue.  This is only needed to support out of order acking from the subscription.  If the consumer is doing in order acking like the JMS API forces, then you can get better performance by using a shared queue /w browsers but track ack positions using a simple map/index.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)