Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.250.139 is neither permitted
 nor denied by domain of jw@yahoo-inc.com)
Date: Thu, 1 Aug 2013 17:56:41 -0700 (PDT)
From: Jake Choi <jw@yahoo-inc.com>
To: users@activemq.apache.org
Message-ID: <1375405001076-4670035.post@n4.nabble.com>
In-Reply-To: <1375401657063-4670033.post@n4.nabble.com>
References: <1375114612647-4669838.post@n4.nabble.com>
 <CAKS7T5NZgkKY0TCys6St+73FwFm3tRzwLWvth+mHjHH9KjV_qQ@mail.gmail.com>
 <1375225948718-4669896.post@n4.nabble.com>
 <1375375672931-4670001.post@n4.nabble.com>
 <CAKS7T5NLFqSRKJf2bUsks0FiaA9mfHE_hHOh4_rAC6m3zFQddg@mail.gmail.com>
 <CAKS7T5NWQ7UEiwWCbUTGKkUm4mp4t=Tvb9+A-oWDbj+eyWu0+g@mail.gmail.com>
 <1375397810293-4670029.post@n4.nabble.com>
 <CAKS7T5N2Ha_tbMcMME9JVPgL3VfZbSan7Ptuzm7YpqDY6zxf5w@mail.gmail.com>
 <1375401478365-4670031.post@n4.nabble.com>
 <1375401657063-4670033.post@n4.nabble.com>
Subject: Re: cursor memory usage/limit vs memory usage/limit
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think I got it.  With activemq-core-5.7.0, there's a clear difference
between doing and non-doing the following:

policyEntry.setPendingDurableSubscriberPolicy(new
StorePendingDurableSubscriberMessageStoragePolicy());

One resulting difference was that, StoreDurableSubscriberCursor#topics
member variable (TopicStorePrefetch map) was empty when I used the above
setting.  This was because the instance of  StoreDurableSubscriberCursor
class is created 3 times with the above line, while it was created only once
without the above line.  Moreover, when the above line is used,
TopicStorePrefetch instance is set to the 2nd instance of
StoreDurableSubscriberCursor while the one actually being used during the
processing was the third.  In other words, at runtime, Topic is working
without any TopicStorePrefetch cursor...

I'm looking into the sources more to know why this is happening...


--
View this message in context: http://activemq.2283324.n4.nabble.com/cursor-memory-usage-limit-vs-memory-usage-limit-tp4669679p4670035.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.