activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tarek Hammoud (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (AMQ-5265) JMX destination entires fail due to race condition in MBeanBridgeDestination
Date Tue, 05 May 2015 14:11:59 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tarek Hammoud updated AMQ-5265:
-------------------------------
    Comment: was deleted

(was: Attached is a patch that believe will address the issue.)

> 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)

Mime
View raw message