Solr collections disappear when restarting 'ColdFusion 2016 Add-on Services' service| View in Tracker
Failure Type: Incorrectly functioning
Found In Build/Fixed In Build: 2016,0,04,302561 / 2018.0.0.303787
Priority/Frequency: Normal / All users will encounter
Locale/System: / Win 2008 Server R2 64 bit
Vote Count: 1
Problem Description: When the Solr home path is changed to anywhere other than the default value (C:\ColdFusion2016\cfusion\jetty\multicore), Solr collections listed in the CF Administrator 'ColdFusion Collections' page disappear when the 'ColdFusion 2016 Add-on Services' service is restarted. The actual collection files are still there, but no record of their existence shows in the CF Administrator. At this point, if the collection is queried, an error is thrown, stating that the collection does not exist. But if an attempt to recreate the collection is made, another error is thrown (org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException), presumably because a record of the collection does actually exist somewhere. Then, after this error occurs, the collection does now reappear in the CF Administrator, and is searchable. This happens in both the CF Administrator and programmatically with the <cfcollection> tag. This also happens when the server is rebooted (because the Add-On service is restarted). Steps to Reproduce: 1. Change the Solr home path in the CF Administrator 'Solr Server' page 1. In the CF Administrator 'ColdFusion Collections' page, create a new collection 2. Restart the 'ColdFusion 2016 Add-on Services' service 3. Refresh the 'ColdFusion Collections' page 4. Run a search against the collection with the <cfsearch> tag 5. Try to create the same collection again Actual Result: 1. The new collection (and any others) has disappeared 2. The search throws the following error: Exception Type: coldfusion.tagext.search.CollectionDoesNotExistException: The collection Test does not exist. Exception Detail: The collection you specified does not exists or is not registered with the ColdFusion Search Service. 3. Trying to create the collection again throws the following error: Unable to create Solr collection Test. An error occurred while creating the collection: org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException. Check the Solr logs for more detail. 4. In spite of the error in 3, the collection reappears in the 'ColdFusion Collections' page (original collection, not a new one). Expected Result: Collections survive restarting the 'ColdFusion 2016 Add-on Services' service when the Solr home path is something other than the default value. Any Workarounds: As described above.