Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-20 Thread Daniel Fuchs
On 2/20/15 4:15 AM, Behrooz Nobakht wrote: Hi Daniel, Starting to create a minimal reproduction case for the observations and the discussion, I think I have been able to pin point a bug in our application. Basically, it is a corner case for *properly* closing the FileHandler instance in the end

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Behrooz Nobakht
Hi Daniel, Starting to create a minimal reproduction case for the observations and the discussion, I think I have been able to pin point a bug in our application. Basically, it is a corner case for *properly* closing the FileHandler instance in the end of p2 process. I have a minimal example, with

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Daniel Fuchs
Hi, On 19/02/15 16:30, Behrooz Nobakht wrote: I'd be very happy to introduce an issue. But, I've always failed to be able to create an account on https://bugs.openjdk.java.net/secure/Dashboard.jspa so, for me, the starting point is where I should do this?! If you are not an OpenJDK member then

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Behrooz Nobakht
I'd be very happy to introduce an issue. But, I've always failed to be able to create an account on https://bugs.openjdk.java.net/secure/Dashboard.jspa so, for me, the starting point is where I should do this?! On Thu, Feb 19, 2015 at 3:56 PM, Daniel Fuchs wrote: > Thanks Behrooz. > > Could you

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Daniel Fuchs
Thanks Behrooz. Could you log an issue for this then? If you can attach a small reproducer it will be helpful. There are a bunch of unit tests in the JDK that verify that FileHandler .lck files are correctly deleted - but these tests are all mono-process. I would like to make sure to chase down

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Behrooz Nobakht
Hi Daniel, Thanks for referring to this ticket. Here is what I did. My Java version: java version "1.8.0_40-ea" Java(TM) SE Runtime Environment (build 1.8.0_40-ea-b21) Java HotSpot(TM) 64-Bit Server VM (build 25.40-b24, mixed mode) So, to make this more observable. The p1 process invokes a comm

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Daniel Fuchs
Hi Behrooz, On 19/02/15 13:46, Behrooz Nobakht wrote: The version of Java is irrelevant. We have tested our setup on Java 7 and Java 8 u25/31. We observe the same exception. Ok - then the version is indeed relevant ;-) What you are observing may be a symptom of https://bugs.openjdk.java.net/

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Behrooz Nobakht
Hi Daniel, Thanks for the quick reply. On Thu, Feb 19, 2015 at 1:06 PM, Daniel Fuchs wrote: > Hi Behrooz, > > I have made several fixes WRT to lock files used by FileHandler > recently. Could you please tell us which version of java you > are using when observing this? > > I'll need to analyze

Re: Logging FileHandler: static locks and hardcoded maximum number

2015-02-19 Thread Daniel Fuchs
Hi Behrooz, I have made several fixes WRT to lock files used by FileHandler recently. Could you please tell us which version of java you are using when observing this? I'll need to analyze your issue a bit deeper - and knowing the version (java -version) will help me in not making false assumpti