[
https://issues.apache.org/jira/browse/SOLR-16899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Deparvu reassigned SOLR-16899:
-----------------------------------
Assignee: Alex Deparvu
> 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: 0.5h
> 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: [email protected]
For additional commands, e-mail: [email protected]
