Deadlock situation

[Kenneth Brody]

Quoting Cesar Baquerizo (Fri, 18 Apr 2008 15:29:02 -0400):

> Does anyone have any insight at to what causes this error.  I initially
> thought it was a corrupted file, so I rebuilt the index (D).  When that
> did not work, I created a new index(F), changed the processing and got
> the same error.
>
> The offending line is:
>
>  lookup open = mropenitems  k=ke   i=F -nx
>
>
> *** A System Error Has Occurred ***
>
> Fatal error
> /hd1/appl/filepro/mropenitems/index.F: Deadlock situation detected/avoided

That error indicates one of two possible scenarios:

1 - A true deadlock situation would have occurred.  For example, I have record
     1 locked, and you have record 2 locked.  I attempt to lock record 2, which
     means I will wait until you unlock it.  Then, you attempt to lock  
record 1.
     Because you need to wait for me to unlock it, but I'm already waiting for
     you, if this were allowed, we would both wait forever.

2 - There are too many locks system-wide.

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com