[
https://issues.apache.org/activemq/browse/AMQ-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-921.
----------------------------
Fix Version/s: 5.1.0
(was: 5.2.0)
Resolution: Fixed
> When recovering messages on startup - execution of Store.getMessage is
> executed as many times as many subscribers to this destination there are
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-921
> URL: https://issues.apache.org/activemq/browse/AMQ-921
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 4.1.0
> Environment: Any
> Reporter: Nikolai Penkov
> Assignee: Rob Davies
> Priority: Minor
> Fix For: 5.1.0
>
>
> Fix of issue https://issues.apache.org/activemq/browse/AMQ-878 (when
> recovering gigantic queues) come to a new performance problem. - When
> recovering messages on startup - execution of Store.getMessage (from
> IndirectMessageRefference.incrementReferenceCount) is executed as many times
> as many subscribers to this destination there are. E.g.
> 1. Start of broker with a queue A with a lot of messages
> 2. Queue is recovered from database by creation of IndirectMessageRefferences
> 3. 2 Subscribers connect to recovered queue with two different message
> selectors.
> 4. Messages are loaded from database
> (IndirectMessageRefference.incrementReferenceCount ->
> destinationStore.getMessage) twice - for 2 subscribers...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
