To explain all the things you asked, you should know that Solr has
multiple cores ("search" used by discovery, "statistics" and "oai").
These work completely independently and all of them are started when
the Solr server is started. That's why there's a separate Solr URL
configured for discovery, statistics and oai - each points to a
different core. I checked the codebase and solr-statistics.server is
used only by the Solr client in DSpace. That means it doesn't control
where the Solr server listens, the Solr server is simply always
started on localhost, regardless of value of this property. If you
change the property to point elsewhere, the local core _should_ simply
be unused (can you confirm that by querying it for number of
documents? It's the "*:*" query and the numFound attribute in
response.).That said, I can't think of the reason why it doesn't work. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
