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

["Gary Tully (JIRA)" <ji...@apache.org>]

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

Gary Tully edited comment on AMQ-5265 at 6/15/15 10:53 AM:
-----------------------------------------------------------

[~Hauenstein] peek at https://github.com/apache/activemq/blob/138e52b08c2f49b730817932a6e63f2a135854f1/activemq-unit-tests/src/test/java/org/apache/activemq/network/DuplexNetworkMBeanTest.java for some unit test inspiration, or other tests in that package


was (Author: gtully):
[~Hauenstein] peek at https://github.com/apache/activemq/blob/138e52b08c2f49b730817932a6e63f2a135854f1/activemq-unit-tests/src/test/java/org/apache/activemq/network/DuplexNetworkMBeanTest.java for some unit test inspiration

> 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
>             Fix For: 5.10.1, 5.11.0
>
>         Attachments: AMQ-5265.patch, activemq.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.3.4#6332)