k should be changed to not throw the exception,
> >> but rather do a best effort - call delete() but don't respond to its
> return
> >> value. I'll change that on 3x, I'm not sure if a backport to 3.0.x is
> needed
> >> (doesn't seem to justify
throw new IOException("Cannot delete " + lockFile);
}
We have seen this exception path once in the wild (on a Windows box).
I can work around this with a custom LockFactory but thought I should check
if I'm reading the code right.
Cheers,
Ted
--
Ted McFadden
Chief
