cancel
Showing results for 
Search instead for 
Did you mean: 

random severe error in 4.2

sharifu
Confirmed Champ
Confirmed Champ
Just upgraded from 4.0d and I am getting following randomly or probably on every page i browse in share


SEVERE: Incorrect ACL set269675 CacheEntry [dbid=89986, leaf=0, path=269675, aclid=0, owner=0]
java.lang.IllegalStateException: Cache position check failed
   at org.alfresco.solr.AlfrescoSolrEventListener$AbstractCacheMatch.checkCachePosition(AlfrescoSolrEventListener.java:1899)
   at org.alfresco.solr.AlfrescoSolrEventListener$Match.updateCache(AlfrescoSolrEventListener.java:2553)
   at org.alfresco.solr.AlfrescoSolrEventListener.newSearcher(AlfrescoSolrEventListener.java:332)
   at org.apache.solr.core.SolrCore$4.call(SolrCore.java:1163)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
   at java.util.concurrent.FutureTask.run(FutureTask.java:166)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
   at java.lang.Thread.run(Thread.java:722)


I am not using solr but lucene if that helps.
2 REPLIES 2

andy
Champ on-the-rise
Champ on-the-rise
Hi

It would seems you are still running the SOLR web app and building the solr index 🙂

There are a few cases in the community product when this can occur. Non are fatal. The cache double check is there to make sure we have reverse enginering the index merge correctly. If this check fails (mostly on deciding on how emtpy segments - with only deleted docs in - have been merged up) it gives up, throws the cache awayand build it from scratch.

If you know what kind of things you were doing to get the issue that would help us too …

Andy

sharifu
Confirmed Champ
Confirmed Champ
The following is set in my global properties file, which I have used throught the previous versiona that I have used.


### Solr indexing ###
index.subsystem.name=lucene
dir.keystore=${dir.root}/keystore
solr.port.ssl=8443

I only go tthis error on 4.2, never seen it on 4.0d or 3.4d.

I get this straight after I restart and just normal browsing in share. Can't remember anything specific at the moment but shall post if I do notice anything.