AnsweredAssumed Answered

[SOLR] NamespaceException: URI has already been defined

Question asked by s_turner on Jun 11, 2014
Latest reply on Jun 11, 2014 by s_turner
Hi,

I've defined a custom model and it's seems to all be working in Alfresco - my aspect is available to add and use, custom properties appear on content items and advanced search form, there are no errors in alfresco.log. Problem is SOLR search is refusing to index. In solr.log I just get the repeated error:

00:00:00,089 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-alfresco threw an unhandled Exception:
org.alfresco.service.namespace.NamespaceException: URI quotall.model has already been defined
   at org.alfresco.repo.dictionary.NamespaceDAOImpl.addURI(NamespaceDAOImpl.java:253)
   at org.alfresco.repo.dictionary.DictionaryDAOImpl.putModelImpl(DictionaryDAOImpl.java:327)
   at org.alfresco.repo.dictionary.DictionaryDAOImpl.putModelIgnoringConstraints(DictionaryDAOImpl.java:294)
   at org.alfresco.solr.AlfrescoSolrDataModel.putModel(AlfrescoSolrDataModel.java:670)
   at org.alfresco.solr.tracker.CoreTracker.loadModel(CoreTracker.java:4014)
   at org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1824)
   at org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
   at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
   at org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
   at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
   at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)

My customModel.xml file contains the definition of my model, (attached as customModel.txt). It's in the shared/classes/alfresco/extension folder and that's the only place I've made changes for my custom model. There are no other custom models defined.

I've attempted to reindex SOLR but that just gives this same error. I'm using Alfresco Community 4.2 and this custom model is the only change I've made to Alfresco after a standard install.

Anybody have any idea why SOLR is having this problem?

Thanks,
Stuart


Attachments

Outcomes