[AMQ-5265] JMX destination entires fail due to race condition in MBeanBridgeDestination

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.9.1, 5.10.0
• Fix Version/s: 5.10.1, 5.11.0
• Component/s: Broker
• Patch Info: Patch Available
• Assignee: Dejan Bosanac
• Reporter: Jeff Genender
• Created: 08/Jul/14 21:03
• Updated: 16/Oct/23 09:37
• Resolved: 09/Jul/14 14:58

Description

JMX statistics on destinations creates a race condition in the MBeanBridgeDestination's onInboundMessage, onOutboundMessage, and the purgeInactiveDestinationView task. If the task fires and removes the objectName while the onInboundMessage or onOutboundMessage fires, it will spit out warnings of it already being created if multiple threads are running. The fix is to properly synchronize in the purgeInactiveDestinationView and also be sure it cleans up itself in the destinationObjectNameMap.

Patch is attached as is a git pull request (for whatever is easier)