In order to get any useful help, it would be nice to know what you are trying to do, and (most importantly) what commons component is giving you the problem :-). The traditional approach is to put a prefix on your subject line -- for commons package "foo" it would be:
[foo] avoiding locking It's also generally helpful to see the entire stack trace, not just the exception message itself. Craig On Thu, 11 Nov 2004 17:27:19 -0500, Luke Shannon <[EMAIL PROTECTED]> wrote: > What can I do to avoid locking issues? > > Unable to execute incremental update Lock obtain timed out: > Lock@/usr/tomcat/jakarta-tomcat-5.0.19/temp/lucene-398fbd170a5457d05e2f4d43210f7fe8-write.lock > > Thanks, > > Luke > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
