Rupert Westenthaler created STANBOL-908:
-------------------------------------------
Summary: ManagedSolrServer does not use system specific file
separators when initialising SolrCores
Key: STANBOL-908
URL: https://issues.apache.org/jira/browse/STANBOL-908
Project: Stanbol
Issue Type: Bug
Components: Commons
Affects Versions: commons-0.11.0
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
During the copying process of a provided SolrCore (in an {name}.solrindex.zip
file) a '/' is used to search for the context used to determine the target
folder for files provided by the ArchiveInputStream.
Because of that copying fails in case the archive does not use forward slashes
as path separators of Archive entries. Users affected by this will encounter a
java.lang.IllegalArgumentException: The parsed File
'<..root..>\stanbol\indexes\default\<..sitename..>-2013.02.02' MUST represent a
Directory!
at
org.apache.stanbol.commons.solr.SolrServerAdapter$SolrCoreProperties.setCoreDir(SolrServerAdapter.java:856)
during the initialisation of the SolrCore. In addition the log will contain
WARN level loggings like
03.02.2013 20:50:44.625 *INFO* [Thread-40]
org.apache.stanbol.commons.solr.managed.impl.ManagedSolrServerImpl ... start
to ACTIVATE Index <sitename> on ManagedSolrServer
03.02.2013 20:50:44.627 *WARN* [Thread-40]
org.apache.stanbol.commons.solr.utils.ConfigUtils Context <sitename>/ not found
in resource <sitename>\conf\admin-extra.html -> ignored!
03.02.2013 20:50:44.627 *WARN* [Thread-40]
org.apache.stanbol.commons.solr.utils.ConfigUtils Context <sitename>/ not found
in resource <sitename>\conf\elevate.xml -> ignored!
To solve this issue paths of archive entries need to be converted to always use
system specific separators.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
