RE: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

am.close may throw > IOException if called twice and underlying flush or close fails > From: chris.hega...@oracle.com > Date: Thu, 22 Jan 2015 09:01:10 + > CC: core-libs-dev@openjdk.java.net > To: nathan.a.clem...@hotmail.com > > On 21 Jan 2015, at 22:37, Nathan Cl

RE: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

Hi Chris, Thanks for your help on this one! Will this be backported to JDK 8, or is that not allowed because of the spec change? Thanks, Nathan > Date: Mon, 22 Dec 2014 14:13:18 + > From: chris.hega...@oracle.com > To: core-libs-dev@openjdk.java.net; nathan.a.clem...@hotmail.com > Subject

RE: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

Hi, What's the process for finalizing a decision and getting this bug fixed? Apologies if I'm violating a social norm by asking this - I'm new to this process and I'm not sure exactly how decisions are made. Thanks, Nathan > From: nathan.a.clem...@hotmail.com > To: chris.hega...@oracle.com; p

RE: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

Hi, I'd be happy with any of the solutions discussed here. In our case, we're only calling close() multiple times as a result of the way that try-with-resources works with wrapped streams. Thanks, Nathan Subject: Re: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if cal

RE: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

Regards, Nathan > Date: Fri, 5 Dec 2014 02:02:45 +0100 > From: e...@zusammenkunft.net > To: core-libs-dev@openjdk.java.net > Subject: Re: [PATCH] JDK-8054565: FilterOutputStream.close may throw > IOException if called twice and underlying flush or close fails > > Am Fri

RE: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

Hi, My problem is definitely not related to multi-threaded use. The test shows basically the same code that we have in production that experienced the problem. The stream is used from a single thread in a try-with-resources block. I don't see that this change is any more risky than the change

RE: [PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

m.close may throw > IOException if called twice and underlying flush or close fails > > Hi Nathan, > > This list removes attachments. > Can the diff's be inlined in the email? > > Thanks, Roger > > On 12/4/2014 1:18 AM, Nathan Clement wrote: > > Hi, > > &g

[PATCH] JDK-8054565: FilterOutputStream.close may throw IOException if called twice and underlying flush or close fails

Hi, Here is my suggested fix for the FilterOuputStream issue in JDK-8054565. I have been running this fix in my applications for several weeks (by adding it to the bootstrap classpath) and it solves my issue. The fix creates a new member field to remember whether close has already been called

Java 8 FilterOutputStream.close() bug

.com/questions/25175882/java-8-filteroutputstream-exception. Do people agree that this is a bug? If so, what is the process for fixing it? Thanks, Nathan Clement