John Call created SOLR-7705:
-------------------------------
Summary: CoreAdminHandler Unload no longer handles null core name.
Key: SOLR-7705
URL: https://issues.apache.org/jira/browse/SOLR-7705
Project: Solr
Issue Type: Bug
Components: clients - java
Affects Versions: 5.2, 5.1, 5.0, 4.10
Environment: Windows 8 and Windows Server 2012 R2
Reporter: John Call
Priority: Minor
Fix For: Trunk, 5.2, 5.1, 5.0, 4.10
Pre 4.10 If a null core name was passed in it would be handled as a bad request
with error message "No such core exists [ null ]". From 4.10 onwards an unload
call goes to CoreContainer unload where the first action taken is removing the
core from coreInitFailures which throws when given null and instead of
returning the expected BadRequest "Cannot unload non-existent core [null]" it
returns InternalServerError "java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.replaceNode(Unknown Source)
at java.util.concurrent.ConcurrentHashMap.remove(Unknown Source)
at org.apache.solr.core.CoreContainer.unload(CoreContainer.java:661)..."
This was found due to mixing up query parameter "name" used in create vs "core"
in unload. As a result this is easily reproducible with
http://localhost:8983/solr/admin/cores?action=UNLOAD&name=core0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
