Resource leak

[K Sekar]

Hi,
We heard about the case where the application will cause resource leakage
if we fail to close the resources properly.

Existing snippet :

try{

// using I/O Stream

// closing the resource

}
catch(IOException e){
//Log the Exception
}

Assume that there exists a issue(say I/O operations) which prevents the execution of the program to close the resource.

Modified snippet :

try{

// using I/O Stream

// closing the resource

}
catch(IOException e){
//Log the Exception
}
finally{
// null check
// close the resource
}

The thing is I need to replicate the problem so as to test
whether the introduction of finally block forces the program
to close the resource.

Can anyone help me in replicating the resource leakage problem?


Thanks In Advance.
Kannan

[Rob Spoor]

It's quite easy:

FileOutputStream fos = new FileOutputStream("Some File");
try
{
    fos.write(13); // enter
    throw new IOException("Just felt like it");
}
catch (IOException e)
{
    e.printStackTrace();
}
finally
{
    fos.close();
}
System.in.read();

Try the following with and without the closing:
- start the program
- delete the file from Windows
- press enter in the program

If you don't close the stream Windows cannot delete the file because it's still in use (until the Java program exists, hence the System.in.read()).

[Nitesh Kant]

Howdy kannan!

We being a very friendly community, do not have much rules but there is a naming policy that we are very strict about!
Unfortunately, your display name does not follow the policy. Please take a moment to change the same.

I see that you have been in the ranch for long. Is it so that you have been bitten by the this google chrome bug?

[Rob Spoor]

The name was Kannan Dhanasekaran before, so that's why there was no previous warning.

[K Sekar]

Many Thanks Prime.

[Rob Spoor]

Kannan, are you by chance using Google Chrome as your browser? It has a bug that sometimes sets your display name even though you don't want it to.

Can you please change it back, and keep that in mind while using Chrome?

[K Sekar]

Ya Sure .

[Nitesh Kant]

Kannan, I do not think you understood what we are asking you to do. Your display name still violates the naming policy.
It may be because of the google chrome bug but please take a moment to change it.