[email protected]
> Subject: Re: Zombie FileHandler locks can exhaust all available log file
> locks.
>
> Hi Jason,
>
> Thanks for the feedback!
>
> On 6/24/14 7:08 PM, Jason Mehrens wrote:
>> Daniel,
>>
>>
>> With regard to J
o: [email protected]; [email protected];
[email protected]
Subject: Re: Zombie FileHandler locks can exhaust all available log file locks.
On 6/23/14 4:53 PM, Alan Bateman wrote:
On 23/06/2014 10:48, Daniel Fuchs wrote:
:
All in all - I feel our best options would be to revert to
4 17:13:04 +0200
> From: [email protected]
> To: [email protected]; [email protected];
> [email protected]
> Subject: Re: Zombie FileHandler locks can exhaust all available log file
> locks.
>
> On 6/23/14 4:53 PM, Alan Bateman wrote:
>> On 23/06
On 6/23/14 4:53 PM, Alan Bateman wrote:
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
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 look
-
Date: Mon, 23 Jun 2014 11:48:18 +0200
From: [email protected]
To: [email protected]; [email protected]
Subject: Re: Zombie FileHandler locks can exhaust all available log
file locks.
Hi Jason,
Looking at the diff for 6244047 - I see that, as you
[email protected]
Subject: Re: Zombie FileHandler locks can exhaust all available log file locks.
Hi Jason,
Looking at the diff for 6244047 - I see that, as you pointed
out, the unwanted behavior described comes from the fact that
the new code is using CREATE_NEW - which prevents the &#
23 Jun 2014 11:48:18 +0200
> From: [email protected]
> To: [email protected]; [email protected]
> Subject: Re: Zombie FileHandler locks can exhaust all available log file
> locks.
>
> Hi Jason,
>
> Looking at the diff for 6244047 - I see that
Hi Jason,
Looking at the diff for 6244047 - I see that, as you pointed
out, the unwanted behavior described comes from the fact that
the new code is using CREATE_NEW - which prevents the 'zombie
lock files' from being reused.
I am not an expert in file locks - but I wonder whether we
could rever
Daniel, Jim,
In JDK8 the FileHandler file locking was changed to use FileChannel.open with
CREATE_NEW. If the file exists (locked or not) the FileHandler will rotate due
to safety concerns about writing to the same log file. The FileHandler has an
upper bound of 100 as the number of file locks
10 matches
Mail list logo
