Producer hangs on durable subscribe as Usage memory runs over

• Key: AMQ-1449
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Rob Davies
• Reporter: Nicky Sandhu
• Component/s: Broker
• Fix Version/s: 5.0.0

Description

Broker hangs on a durable subscribe when producer is disconnected violently (System.exit()). I have included the test files to reproduce the problem

WARNING: The test cases included can be patched against activemq-core but are not unit tests. Do the following sequence

1.) Run the junit test DurableProducerConsumerBrokerTest. This starts a broker
2.) Run the junit test DurableProducerConsumerTest. It will exit with System.exit midway thru running the test
3.) Rerun the junit test DurableProducerConsumerTest...It should hang the second time around

Note: If you use the log4j.properties included in the patch you would see the Usage memory as it rises above 70 to 99+ in the second run.

Comments

[Nicky Sandhu]

Started in forum thread http://www.nabble.com/Usage-Manager-for-durable-offline-subscriber-t4572289s2354.html#a13051280

[Nicky Sandhu]

TopicStorePrefetch has a system usage manager that is not used by Message (broker.region package). It instead uses the increment/decrement to inform the regionBroker's system usage manager which happens to be a different one.

So the listener implemented by DurableTopicSubscription never results in an actual call back and hence the leak ??

I don't understand this one completely but i hope it helps whoever looks at this issue

[Rob Davies]

Fixed by svn revision 587033

[Nicky Sandhu]

Thanks Rob! It does great under the performance tests as well. Any thoughts on how to include/modify these tests for the build ?