On 21/08/07, Christian Voelker <[EMAIL PROTECTED]> wrote: > > Lock obtain timed out: [EMAIL PROTECTED]:\Tomcat 6.0\temp\lucene- > e575723f586b663d697cde458e2fa736-write.lock > > Why cant it get a write lock in that moment? I dont know > about the inner working of lucene, but the file name looks > as if it were created per thread.
I suspect (though couldn't verify in the 30 seconds I spent looking at the docs) that Lucene can't support concurrent index writes and has to lock for each write, meaning some time out waiting. See: http://wiki.apache.org/lucene-java/LockObtainTimedOut As of 1.5, it will be possible to have all indexing performed in a separate, dedicated thread which should make this problem go away if you use the asynchronous JMS configuration. Rob ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
