You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/09/03 13:51:55 UTC

[jira] [Resolved] (CAMEL-6695) mbeansRegistered in DefaultManagementAgent isn't ThreadSafe

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

Claus Ibsen resolved CAMEL-6695.
--------------------------------

    Resolution: Fixed
    
> mbeansRegistered in DefaultManagementAgent isn't ThreadSafe
> -----------------------------------------------------------
>
>                 Key: CAMEL-6695
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6695
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.10.6, 2.11.1
>            Reporter: Achim Nierbeck
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.10.7, 2.11.2, 2.12.0
>
>
> This is more or less a "corner-case" I stumbled upon, though
> the HashSet/HashMap (2.5/2.10 camel versions) in the DefaultManagementAgent containing the registered Mbean _mbeansRegistered_ isn't Thread-Safe. 
> This has been an issue for us while using the ProducerTemplate in a wrongful way, by instantiating the ProducerTemplate during every Route run. 
> As this might be a common mistake by users I'd suggest to improve the _mbeansRegistered_ by using a Synchronized Map.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira