lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-918) Thread safety issue in SolrCore.infoRegistry
Date Fri, 19 Dec 2008 06:05:44 GMT

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

Shalin Shekhar Mangar commented on SOLR-918:
--------------------------------------------

Alright. When JMX is enabled, it uses the JmxMonitoredMap which extends ConcurrentHashMap
so order is not maintained anyway. Let's stick with ConcurrentHashMap, I'll scan through the
code and remove all synchronization during iteration and update the javadocs.

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


Mime
View raw message