You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/09/12 21:24:00 UTC

[jira] [Commented] (SOLR-16899) CoreAdminOp are statically registered in CoreAdminHandler, preventing more than one Solr instance in the same JVM

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

ASF subversion and git services commented on SOLR-16899:
--------------------------------------------------------

Commit 4989aadf2794d688879353fd8219a69190ad1049 in solr's branch refs/heads/main from Vincent P
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=4989aadf279 ]

SOLR-16899: Do not statically register ops in CoreAdminHandler (#1892)

Co-authored-by: Vincent Primault <vp...@salesforce.com>
Co-authored-by: Alex Deparvu <st...@apache.org>

> CoreAdminOp are statically registered in CoreAdminHandler, preventing more than one Solr instance in the same JVM
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-16899
>                 URL: https://issues.apache.org/jira/browse/SOLR-16899
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 9.2.1
>            Reporter: Cédric Damioli
>            Assignee: Alex Deparvu
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Since Solr 9.1 and SOLR-16282, one may register custom CoreAdminOp in solr.xml
> Custom CoreAdminOp are stored in a static Map in CoreAdminHandler
> Before 9.1 I could write eg. unit tests, each test starting its own EmbeddedSolrServer
> Since 9.1, the second EmbeddedSolrServer try to load its own CoreAdminHandler and fail, complaining that the CoreAdminOp are already registered
> I actually wonder if it's a bug or a feature, or an implementation constraint, but I don't have found any convenient workaround other than removing my custom CoreAdminOp, going back to the old way of subclassing the CoreAdminHandler 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org