Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 2 Mar 2011 16:16:36 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1341693856.8064.1299082596910.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (AMQ-3196) Speed up initial message delivery for
 offline durable sub with keepDurableSubsActive=true and JDBC store
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Speed up initial message delivery for offline durable sub with keepDurableSubsActive=true and JDBC store
--------------------------------------------------------------------------------------------------------

                 Key: AMQ-3196
                 URL: https://issues.apache.org/jira/browse/AMQ-3196
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Message Store
    Affects Versions: 5.4.2
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.5.0


Follow on from https://issues.apache.org/jira/browse/AMQ-3188
Durablesubs are kept active by default, but their cursors are stopped requiring a read of the store to determine the message backlog. With a large prioritised backlog and th JDBC store, getting the store size can be costly as it requires a full table scan.
Currently there are three calls to getStoreSize, there should be only one when the sub is initially created.
The implication is that on reactivation of an offline durable sub, there is a delay of an additional potentially slow jdbc call before dispatch resumes.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira