cancel
Showing results for 
Search instead for 
Did you mean: 

SolrTrackerScheduler throwing SchedulerException.

satheeshkumar
Champ in-the-making
Champ in-the-making
Hi All,

I am using Alfresco Community Edition 5.0.c.
I have created several customizations and applied amps to both alfresco and share. I am able to make the application up and running.
But recently I started getting one weird error, I really have no idea why I am getting this error, I am able to access my application without any issues, but only thing is this ERROR keeps popping in the logs every 20 seconds.

I got this error last week also, since I was into the initial stage of development, I just went ahead and reinstalled the entire application and created the sample data. This error was not there for a week's time.
Now I got this error again, I'm worrying how to get rid of this error, I tried googling and searching in this forum but could not get a resolution for this.

I am not sure why this error coming and what has caused this error to pile up in the logs.
Can someone please help me to get rid of this error.


2015-05-27 02:29:40,004  ERROR [quartz.core.ErrorLogger] [SolrTrackerScheduler_Worker-3] Job (Solr.CoreWatcher threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: org.alfresco.service.cmr.dictionary.DictionaryException: 04272315 Failed to parse model]
        at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.service.cmr.dictionary.DictionaryException: 04272315 Failed to parse model
        at org.alfresco.repo.dictionary.M2Model.createModel(M2Model.java:102)
        at org.alfresco.repo.dictionary.M2Model.createModel(M2Model.java:88)
        at org.alfresco.solr.tracker.ModelTracker.loadPersistedModels(ModelTracker.java:114)
        at org.alfresco.solr.tracker.ModelTracker.<init>(ModelTracker.java:85)
        at org.alfresco.solr.tracker.CoreWatcherJob.registerForCore(CoreWatcherJob.java:121)
        at org.alfresco.solr.tracker.CoreWatcherJob.execute(CoreWatcherJob.java:74)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
        … 1 more
Caused by: org.jibx.runtime.JiBXException: Error accessing document
        at org.jibx.runtime.impl.XMLPullReaderFactory$XMLPullReader.next(XMLPullReaderFactory.java:293)
        at org.jibx.runtime.impl.UnmarshallingContext.toStart(UnmarshallingContext.java:446)
        at org.jibx.runtime.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java:2750)
        at org.jibx.runtime.impl.UnmarshallingContext.unmarshalDocument(UnmarshallingContext.java:2900)
        at org.alfresco.repo.dictionary.M2Model.createModel(M2Model.java:97)
        … 7 more
Caused by: java.io.EOFException: input contained no data
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at org.jibx.runtime.impl.XMLPullReaderFactory$XMLPullReader.next(XMLPullReaderFactory.java:291)
        … 11 more

5 REPLIES 5

rjohnson
Star Contributor
Star Contributor
There is an error in one of your data model XML documents by the look of it. It looks as if it is trying to read an empty file. I am surprised that Alfresco will come up with that. Do you have any errors in alfresco.log / catalina.out that are not from SOLR.

Hi Johnson,

Thanks for your quick response.

I have only two data models and none of them is throwing any exception, if there is any exception in the data model then the alfresco will not come up right, but in this case it comes up without any issues except that Slor Error.
I restarted alfresco to check for any errors, however I noticed that there is no other error in the catalina.out apart from this solr error,
I have attached the complete log of catalina.out, for your reference.

In the alfresco.log, I do see the below few lines alone, and there is no error at all,

[alfresco@nbalfs2 alfresco-5.0.c]$ more alfresco.log
07:06:23,843 INFO  [org.alfresco.repo.admin] [localhost-startStop-1] Using database URL 'jdbc:postgresql://localhost:5432/alfresco' with user 'alfresco'.
07:06:23,984 INFO  [org.alfresco.repo.admin] [localhost-startStop-1] Connected to database PostgreSQL version 9.3.5
07:06:30,235 INFO  [org.alfresco.repo.management.subsystems.ChildApplicationContextFactory] [localhost-startStop-1] Starting 'sysAdmin' subsystem, ID: [sysAdmin, default]
07:06:30,273 INFO  [org.alfresco.repo.management.subsystems.ChildApplicationContextFactory] [localhost-startStop-1] Startup of 'sysAdmin' subsystem, ID: [sysAdmin, default] complete
07:06:30,291 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] [localhost-startStop-1] Ignoring script patch (post-Hibernate): patch.db-V4.2-metadata-query-indexes
[alfresco@nbalfs2 alfresco-5.0.c]$


Please let me know if you need any additional details in this regard.
Thanks in Advance.

rjohnson
Star Contributor
Star Contributor
Well it looks like you have a dodgy model file in Solr. Now I use 4.2e and thats SOLR 1.4 where as at 5.0c you are using SOLR 4 so things are different.

SOLR has a cached models folder (or did) at alf_data/solr/workspace-SpacesStore/alfrescoModels and alf_data/solr/archive-SpacesStore/alfrescoModels I would check the XML in them to see if anything won't validate using a good XML tool like oXygen.

I assume that this issue comes after you install your APMs. One thing to bear in mind, if you install the amps repeatedly with different data models you can break SOLR if you either change a datamodel property definition or delete a property. Adding a property is OK.

Hi Johnson,

What change I did in my data model was, I moved an existing Property from one type to a custom aspect and configured this custom aspect has mandatory aspects in that type where I have removed this property from.
Will this kind of change also break SOLR?

This change I did because, I was using this property in another type as well, since alfresco throws exception while parsing the DataModel when I have defined a same property for two different types.
so I moved that property into custom aspects and referred this custom aspect in those two types as mandatory aspects.

Please let me know if I do anything wrong here.

Hello.
I was with same error after little changes in my custom model.
For me was solved with deleting of the content in <strong>/alf_data/solr4/model/</strong> and restarting the server.

*Sorry for my English.
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.