here is what it says in the SOLR info page Solr Specification Version: 1.4.0.2009.11.18.10.19.05 Solr Implementation Version: 1.4.1-dev exported - kvinu - 2009-11-18 10:19:05 Lucene Specification Version: 2.9.1 Lucene Implementation Version: 2.9.1 832363 - 2009-11-03 04:37:25
On Thu, Jan 17, 2013 at 1:33 PM, Alexandre Rafalovitch [via Lucene] < ml-node+s472066n4034156...@n3.nabble.com> wrote: > Which version of Solr is it for? > > I had a situation on Solr4, where I basically did not have a directory > that > solr.xml was pointing at for one of the cores. And Solr continued working > but the Admin interface was showing big red banners about configuration > problem. > > So, maybe it was a bug that was fixed for Solr 4? > > Regards, > Alex. > > Personal blog: http://blog.outerthoughts.com/ > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > - Time is the quality of nature that keeps events from happening all at > once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) > > > On Thu, Jan 17, 2013 at 8:03 AM, snake <[hidden > email]<http://user/SendEmail.jtp?type=node&node=4034156&i=0>> > wrote: > > > I will explain the scenario just to avoid all the potential replies > asking > > why. > > > > We run coldFusion servers (windows) which has SOLR built in (running on > > Jetty). > > A customer creates a collection which is stored within their own > webspace, > > they only have read/write access to their own webspace so cannot put > them > > anywhere else. > > > > the default value for abortOnConfigurationError is true. > > This causes endless problems when customers make changes to their > websites > > or cancel their hosting, the collection gets deleted, and SOLR then > crashes > > because it cannot find the config files for that collection. > > We then have to find out which collection is causing the problem, and > > manually remove its entry from solr.xml > > > > Obviously this is a PITA. > > > > In the error output it says. > > > > If you want solr to continue after configuration errors, change: > > <abortOnConfigurationError>false</abortOnConfigurationError> > > in solr.xml > > > > I have tried this, but it has no effect. > > I have also tried putting it in all the solrconfig.xml files > > I tried this > > > > > <abortOnConfigurationError>${solr.abortOnConfigurationError:false}</abortOnConfigurationError> > > > and this > > <abortOnConfigurationError>false</abortOnConfigurationError> > > > > neither had any effect. > > > > How do you get this to work ? > > > > > > > > > > -- > > View this message in context: > > > http://lucene.472066.n3.nabble.com/how-to-get-abortOnConfigurationError-false-working-tp4034149.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://lucene.472066.n3.nabble.com/how-to-get-abortOnConfigurationError-false-working-tp4034149p4034156.html > To unsubscribe from how to get abortOnConfigurationError=false working, click > here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4034149&code=cnVzc0BtaWNoYWVscy5tZS51a3w0MDM0MTQ5fDEwMDg4NTg5MzM=> > . > NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- -- Russ Michaels www.bluethunderinternet.com : Business hosting services & solutions www.cfmldeveloper.com : ColdFusion developer community www.michaels.me.uk : my blog www.cfsearch.com : ColdFusion search engine ** *skype me* : russmichaels -- View this message in context: http://lucene.472066.n3.nabble.com/how-to-get-abortOnConfigurationError-false-working-tp4034149p4034178.html Sent from the Solr - User mailing list archive at Nabble.com.
