lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Wang <>
Subject RE: Urgent Help Please: "Resource temporarily unavailable"
Date Wed, 06 Aug 2008 19:06:33 GMT
Sorry about the double posting. After sending the first email I got a delivery failure notice
from I resent it just to be sure.

Unfornately there is no stack trace in the log. The error object was passed to log4j.error(...),
but no stack trace was printed out.

I thought both IndexReader and IndexWriter are thread safe. Beside, I have no explicit multi-threading
in our own code.

Thanks again!

Alex Wang
CrossView Inc.
Office: 416-281-6888

This message may contain confidential and/or privileged information. If you are not the addressee
or authorized to receive this for the addressee, you must not use, copy, disclose, or take
any action based on this message or any information herein. If you have received this message
in error, please advise the sender immediately by reply e-mail and delete this message. Thank
you for your cooperation.

>-----Original Message-----
>From: Grant Ingersoll []
>Sent: Wednesday, August 06, 2008 2:42 PM
>Subject: Re: Urgent Help Please: "Resource temporarily unavailable"
>What's the full exception?  We don't even know that the exception is
>in Lucene from what you've described.  So, w/o more info, it will be
>pretty hard to help, but if I had to guess, it sounds like you've got
>some threading problems, but who knows.
>Also, no need to send the exact same email 5 minutes apart.
>On Aug 6, 2008, at 2:19 PM, Alex Wang wrote:
>> Hi Everyone,
>> We have an application built using Lucene 1.9. The app allows
>> incremental updating to the index while other users are searching
>> the same index. Today, some search suddenly returns nothing when we
>> know it should return some hits. This does not happen all the time.
>> Sometimes the search succeeded. When checking the logs, I found the
>> following error during searching:
>> Parameter[0]: Resource temporarily unavailable
>> When this error occurred, there were 2 other users deleting
>> documents from the same index. The deletions seemed to succeed, but
>> the search failed.
>> I have no clue what could have caused such error.  Unfortunately
>> there is no further info in the logs. Can someone please shed some
>> light on this? Thanks.
>> Alex
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message