[
https://issues.apache.org/jira/browse/AMQ-5265?focusedWorklogId=885339&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-885339
]
ASF GitHub Bot logged work on AMQ-5265:
---------------------------------------
Author: ASF GitHub Bot
Created on: 16/Oct/23 09:37
Start Date: 16/Oct/23 09:37
Worklog Time Spent: 10m
Work Description: jbonofre closed pull request #114:
https://issues.apache.org/jira/browse/AMQ-5265
URL: https://github.com/apache/activemq/pull/114
Issue Time Tracking
-------------------
Worklog Id: (was: 885339)
Time Spent: 40m (was: 0.5h)
> 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
> Assignee: Dejan Bosanac
> Priority: Major
> Fix For: 5.10.1, 5.11.0
>
> Attachments: AMQ-5265.patch, activemq.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
