[
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.2)
1.3
> 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.3
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
