You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Nikolai Penkov (JIRA)" <ji...@apache.org> on 2006/09/14 12:26:23 UTC

[jira] Created: (AMQ-921) When recovering messages on startup - execution of Store.getMessage is executed as many times as many subscribers to this destination there are

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
         Environment: Any
            Reporter: Nikolai Penkov
            Priority: Minor


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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Assigned: (AMQ-921) When recovering messages on startup - execution of Store.getMessage is executed as many times as many subscribers to this destination there are

Posted by "james strachan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-921?page=all ]

james strachan reassigned AMQ-921:
----------------------------------

    Assignee: Hiram Chirino

> 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
>         Environment: Any
>            Reporter: Nikolai Penkov
>         Assigned To: Hiram Chirino
>            Priority: Minor
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira