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

["Alex Deparvu (Jira)" <ji...@apache.org>]

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

Alex Deparvu resolved SOLR-16899.
---------------------------------
    Fix Version/s: 9.4
       Resolution: Fixed

PR merged. thank you [~vprimault] for the contribution!

> 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
>             Fix For: 9.4
>
>          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