You are viewing a plain text version of this content. The canonical link for it is here.

Posted to solr-dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2008/12/18 00:14:44 UTC

[jira] Commented: (SOLR-918) Thread safety issue in SolrCore.infoRegistry

    [ https://issues.apache.org/jira/browse/SOLR-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657606#action_12657606 ] 

Yonik Seeley commented on SOLR-918:
-----------------------------------

Hmmm, it used to be a synchronized map.
Looks like this bug was introduced back in one of those mega-changes, SOLR-215


> Thread safety issue in SolrCore.infoRegistry
> --------------------------------------------
>
>                 Key: SOLR-918
>                 URL: https://issues.apache.org/jira/browse/SOLR-918
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Shalin Shekhar Mangar
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: SOLR-918.patch
>
>
> SolrCore.infoRegistry is used for keeping a reference to the SolrInfoMBean objects. When JMX is disabled, it is initialized to a LinkedHashMap which is not synchronized.
> We can change this to a ConcurrentHashMap instead of a LinkedHashMap.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.