Zombie FileHandler locks can exhaust all available log file locks.
Alan.Bateman at oracle.com
Mon Jun 23 14:53:59 UTC 2014
On 23/06/2014 10:48, Daniel Fuchs wrote:
> All in all - I feel our best options would be to revert to using
> CREATE, or use CREATE_NEW + DELETE_ON_CLOSE, or not do anything
> and live with the issue.
> Hopefully some nio experts will chime in ;-)
The logging use of FileLock is a bit unusual but looking at it now then
I don't see the reason why it needs to use CREATE_NEW. I don't think
DELETE_ON_CLOSE is suitable here as that work is for transient work
files which isn't the case here. Instead it could use deleteOnExit to
have some chance of removing it on a graceful exit.
BTW: Do you know why locks is Map? Would a Set do?
More information about the core-libs-dev