[
https://issues.apache.org/jira/browse/AMQ-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender updated AMQ-5265:
-------------------------------
Attachment: AMQ-5265.patch
> JMX destination entires fail due to race condition in MBeanBridgeDestination
> ----------------------------------------------------------------------------
>
> Key: AMQ-5265
> URL: https://issues.apache.org/jira/browse/AMQ-5265
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.1, 5.10.0
> Reporter: Jeff Genender
> Attachments: AMQ-5265.patch
>
>
> 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)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
