I have a test case that reproduces the problem. WARNING: This test case is not a unit test even though it uses the junit framework.
Please have a look at https://issues.apache.org/activemq/browse/AMQ-1449. 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#a13102163 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
