[
https://issues.apache.org/jira/browse/SOLR-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216442#comment-14216442
]
Mark Miller commented on SOLR-3774:
-----------------------------------
I duplicated this issue with SOLR-6750.
The way I solved is to not let SolrResourceLoader.inform add any of the same
objects that already exist with a simple check of
!infoRegistry.containsValue(bean). I think it might be a better check than
relying on names because we don't really ever want to add the same object twice
- especially considering SOLR-6586.
{code}
for (SolrInfoMBean bean : arr) {
if (!infoRegistry.containsValue(bean)) {
try {
infoRegistry.put(bean.getName(), bean);
} catch (Exception e) {
log.warn("could not register MBean '" + bean.getName() + "'.", e);
}
}
}
{code}
> /admin/mbean returning duplicate search handlers with names that map to their
> classes?
> --------------------------------------------------------------------------------------
>
> Key: SOLR-3774
> URL: https://issues.apache.org/jira/browse/SOLR-3774
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Attachments: SOLR-3774.patch
>
>
> Offshoot of SOLR-3232...
> bq. Along with some valid entries with names equal to the request handler
> names (/get search /browse) it also turned up one with the name
> "org.apache.solr.handler.RealTimeGetHandler" and another with the name
> "org.apache.solr.handler.component.SearchHandler"
> ...seems that we may have a bug with request handlers getting registered
> multiple times, once under their "real" name and once using their class?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
