Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <13063664.post@talk.nabble.com>
Date: Fri, 5 Oct 2007 10:06:28 -0700 (PDT)
From: Nicky Sandhu <karajdaar@gmail.com>
To: dev@activemq.apache.org
Subject: Re: Usage Manager for durable offline subscriber
In-Reply-To: <13053965.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <13051280.post@talk.nabble.com>
 <371F17F1-4FA1-44DC-8E22-F6B3EFD123D4@gmail.com>
 <13053965.post@talk.nabble.com>


I have been trying to reproduce it in a unit test. No luck so far :( I have
hunch its the client disconnections and reconnections without a proper
session.close

It would be great to have Usage exposed via MBeans. Any plans to do that?

IMHO, reference counting is extremely difficult to implement especially when
increment and decrements are async. Any other strategies under consideration
?

rajdavies wrote:
> 
> oops - that's the latest- must drink coffee before reading email ;)
> Any chance of a test case ?
> 
> cheers,
> 
> Rob
> 
> rajdavies wrote:
>> 
>> Hi Nicky,
>> 
>> which version is that?
>> 
>> 
>> cheers,
>> 
>> Rob
>> 
>> http://rajdavies.blogspot.com/
>> 
>> 
>> 
>> On Oct 5, 2007, at 1:17 AM, Nicky Sandhu wrote:
>> 
>>>
>>> On revision 581885 I turned on debug messages on Usage.java and the  
>>> commented
>>> lines of System.out on Message.java and I see the memory usage  
>>> increase
>>> beyond 100% to something like 16500%. This causes a problem for the  
>>> next
>>> thing that calls Usage.waitForSpace(timeout) and causes an  
>>> indefinite hang
>>>
>>> The Usage.increaseUsage(value) does not check to see if it's full  
>>> and so can
>>> keep allocating even beyond 100%. This seems to be happening a lot  
>>> from
>>> Message.incrementReferenceCount() with no corresponding
>>> Message.decrementReferenceCount() happening.
>>>
>>> In my case it happens when a publishing to a topic (~ 1000 msgs)  
>>> with a
>>> offline durable subscribe with multiple hard disconnects from the
>>> subscriber.
>>> -- 
>>> View this message in context: http://www.nabble.com/Usage-Manager- 
>>> for-durable-offline-subscriber-tf4572289s2354.html#a13051280
>>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>>
>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Usage-Manager-for-durable-offline-subscriber-tf4572289s2354.html#a13063664
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.