RFC: 8132359: JarURLConnection.getJarFile() resource leak when file is not found

[Daniel Fuchs]

Hi Alex,

On 08/05/2020 15:35, Alex Kashchenko wrote:
> On 05/06/2020 01:11 PM, Michael McMahon wrote:
>> Hi,
>>
>> Yes, we've had some discussion about it internally, and while others may
>> yet have an opinion, I think this approach is a reasonable one, with a 
>> spec change
>> that captures the behavior.
> 
> I've created a CSR for this issue listing the "return null" variant 
> above and "disable cache" as alternatives:
> 
> https://bugs.openjdk.java.net/browse/JDK-8244650
> 
> The wording for getJarFile() specification currently doesn't specify 
> what happens, when entry doesn't exist. If it is better to change this 
> wording - I would appreciate a guidance on that.

I believe some sort of spec change will be needed, if only to justify
challenging the JCK. Currently, the proposed change trips the following
test:

TestCase: [JarURLConnectionT216] FAIL->getManifest() did not throw 
expected IOException for 
jar:file:/JCK-runtime-15/tests/api/java_net/JarURLConnection//jardir/T11.jar!/NOJARENTRY.class

best regards,

-- daniel

> 
>>
>> [...]
>>
>