topic After completion (committed) Lucene exception in Alfresco Archive

After completion (committed) Lucene exception

omkaaraa — Tue, 18 Dec 2012 09:22:09 GMT

Hi,I am using Alfresco 3.0 (Community) , tomcat 5.5 and UNIX. My Java program reads document from disk (one system) and upload those documents to alfresco (another system). After loading some documents (not fixed how many, some times more than10K , some times less than 500) In catelina log, I can s

Re: After completion (committed) Lucene exception

openpj — Tue, 18 Dec 2012 09:45:16 GMT

Probably you have a deadlock for accessing in read/write Lucene indexes on your file system.

Try to increase the maximum number of your file handlers on your operating system.
It seems that you have a problem during the concurrent operation for reading indexes but it depends on your operating system.

Hope this helps.

Re: After completion (committed) Lucene exception

omkaaraa — Wed, 19 Dec 2012 06:57:19 GMT

Thank you for reply
I checked how to increase number of file handlers in UNIX. Probably you are talking about File descriptor. Findings are:

We can increase File handler size at user level.
and session level too.

I will change it at user level and will monitor whether I am getting same error or not. Will let you know soon.

Some more information about same program:
I am running 10 threads to upload documents.
10 separate Java threads are picking up files and uploading documents on Alfresco server.

Re: After completion (committed) Lucene exception

omkaaraa — Wed, 19 Dec 2012 14:36:05 GMT

Now file handler size is :
$ ulimit -Hn
32768
$ ulimit -Sn
32768

Still same error.. Also sometimes below exceptions..

When this lucene related exception occurrs.. other exception also occurs. Otherwise everything goes smooth.
I think root cause is this lucene exception. We took backup of index and restarted as suggested on this forum. Nothing worked.

So any other suggestion (Except upgration of Alfresco version) ?

Re: After completion (committed) Lucene exception

sbonami — Thu, 11 Aug 2016 13:11:33 GMT

I noticed your thread was almost 4 years old, but I have the same problem. Did you find a solution perhaps?