You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jeff Genender (JIRA)" <ji...@apache.org> on 2014/07/08 23:04:05 UTC
[jira] [Created] (AMQ-5265) JMX destination entires fail due to
race condition in MBeanBridgeDestination
Jeff Genender created AMQ-5265:
----------------------------------
Summary: 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.10.0, 5.9.1
Reporter: Jeff Genender
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)