AnsweredAssumed Answered

Alfresco 4.0a upgrade - SOLR indexing errors

Question asked by andrewlove on Oct 12, 2011
Latest reply on Jan 9, 2012 by andy
I have carried out a test upgrade of an existing Alfresco Community v3.4c deployment to Alfresco v4.0a Community.  This is running on CentOS v6.0.

As part of the migration I switched the search sub-system from Lucene to SOLR, as per the documentation. Specifically I edited and set:
I also deleted any existing lucene indexes from the alf_data directory prior to firing up Alfresco v4.0a.

Having started the v4.0a deployment everything migrated smoothly and I can use the repository and Share.  My only problem is searching and my logs are filling up with the following error:

INFO: Server startup in 154136 ms
Oct 11, 2011 6:20:36 PM org.quartz.core.JobRunShell run
SEVERE: Job Solr.CoreTracker-archive threw an unhandled Exception:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
   at java.lang.String.substring(
   at org.alfresco.solr.SolrLuceneAnalyser.findAnalyser(
   at org.alfresco.solr.SolrLuceneAnalyser.tokenStream(
   at org.alfresco.solr.SolrLuceneAnalyser.tokenStream(
   at org.apache.lucene.analysis.Analyzer.reusableTokenStream(
   at org.apache.solr.schema.IndexSchema$SolrIndexAnalyzer.reusableTokenStream(
   at org.apache.lucene.index.DocInverterPerField.processFields(
   at org.apache.lucene.index.DocFieldProcessorPerThread.processDocument(
   at org.apache.lucene.index.DocumentsWriter.updateDocument(
   at org.apache.lucene.index.DocumentsWriter.updateDocument(
   at org.apache.lucene.index.IndexWriter.updateDocument(
   at org.apache.lucene.index.IndexWriter.updateDocument(
   at org.alfresco.solr.AlfrescoUpdateHandler.addDoc(
   at org.alfresco.solr.tracker.CoreTracker.indexNode(
   at org.alfresco.solr.tracker.CoreTracker.trackRepository(
   at org.alfresco.solr.tracker.CoreTracker.updateIndex(
   at org.alfresco.solr.tracker.CoreTrackerJob.execute(
   at org.quartz.simpl.SimpleThreadPool$

Does anyone have any idea where I've gone wrong or what may be causing this error?

Many thanks