Topics leaked in DestinationMapNode

• Key: AMQ-1319
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Jonas Lim
• Reporter: Manuel Teira
• Component/s: Broker
• Affects Version/s: 4.1.1
• Fix Version/s: 4.1.2

Environment

activemq from svn branch 4.1
Standalone broker running with JDBC persistence and no journal

Description

DestinationMapNode removeAll method is not erasing the given Topic from all the anyChild nodes it should. This leads to severe memory leaks in situations where a lot of advisory topics are created (i.e. working with temporary queues).

As this effect is not found in the trunk, I've found that the related code was heavily changed in r478324. So, I've backported that changes (related with AMQ-1068) to 4.1 branch. I had to make some additional changes to make the DestinationMapNode class honour the contract if the new DestinationNode interface as needed for java 1.4.

I'm attaching the patch.

Comments

[Jonas Lim]

patch applied in 4.1 branch r559023