Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: "Newman, Billy" <Billy.Newman@itt.com>
To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>
Date: Wed, 13 May 2009 16:04:55 -0400
Subject: OS not allowing me to get native fs lock
Thread-Topic: OS not allowing me to get native fs lock
Thread-Index: AcnUBhXxVZlnfDfwS7GtYzy6Nj5flg==
Message-ID: 
 <F0DB6EA8DC0F594B83F2CA60C7E4E8BA2D368AB596@IIWCBO-EMB1.iiw.de.ittind.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_F0DB6EA8DC0F594B83F2CA60C7E4E8BA2D368AB596IIWCBOEMB1iiw_"
MIME-Version: 1.0

--_000_F0DB6EA8DC0F594B83F2CA60C7E4E8BA2D368AB596IIWCBOEMB1iiw_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I know that this is not really a lucene problem but looking around I have n=
ot been able to find much about it.

I recently ran into a problem where I cannot obtain a lock due to a problem=
 with native file system locks.  The strange thing is that this was working=
 a few days ago and I have just started seeing problems today.  As far as I=
 know nothing has changed, but I am sure something did actually change to c=
ause this problem I am just not sure where to start looking.

I get a LockObtainedFailedException... java.io.IOException: protocol family=
 not supported...
Caused by..sun.nio.ch.FileChannelImpl.lock0(NativeMethod)

Any ideas on were to start looking would be extremely helpful. I am running=
 on Redhat 4.

________________________________
This e-mail and any files transmitted with it may be proprietary and are in=
tended solely for the use of the individual or entity to whom they are addr=
essed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely =
those of the author and do not necessarily represent those of ITT Corporati=
on. The recipient should check this e-mail and any attachments for the pres=
ence of viruses. ITT accepts no liability for any damage caused by any viru=
s transmitted by this e-mail.

--_000_F0DB6EA8DC0F594B83F2CA60C7E4E8BA2D368AB596IIWCBOEMB1iiw_--