[jira] [Work logged] (AMQ-5265) JMX destination entires fail due to race condition in MBeanBridgeDestination

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-5265?focusedWorklogId=562215&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562215 ]

ASF GitHub Bot logged work on AMQ-5265:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Mar/21 08:39
            Start Date: 08/Mar/21 08:39
    Worklog Time Spent: 10m 
      Work Description: lucastetreault commented on pull request #114:
URL: https://github.com/apache/activemq/pull/114#issuecomment-792580779


   Can one of the admins verify this patch?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 562215)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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.3.4#803005)