https://issues.apache.org/bugzilla/show_bug.cgi?id=52723
--- Comment #6 from Konstantin Kolinko ---
(In reply to comment #5)
1. BufferedOutputStream does not deserve closing, because it is in memory only.
No native resources are leaking.
- ObjectOutputStream would never need to be closed. If an
https://issues.apache.org/bugzilla/show_bug.cgi?id=52723
--- Comment #5 from liangg...@sei.pku.edu.cn ---
Hi, Konstantin, can you explain more about your new comment (Comment 4)?
Does the BufferedOutputStream temp object need to be closed in this code piece?
--
You are receiving this mail becau
https://issues.apache.org/bugzilla/show_bug.cgi?id=52723
--- Comment #4 from Konstantin Kolinko ---
My comment 2 was wrong. I missed that the original code closes oos (which is
always null there). It should have closed the file stream instead.
oos constructor can throw IOException because it wr
https://issues.apache.org/bugzilla/show_bug.cgi?id=52723
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=52723
--- Comment #2 from Konstantin Kolinko 2012-03-21
00:18:14 UTC ---
> When the ObjectOutputStream object is created unsuccessfully but the temp
BufferedOutputStream object is created successfully, the temp object will be
leaked.
Buffered
https://issues.apache.org/bugzilla/show_bug.cgi?id=52723
Mark Thomas changed:
What|Removed |Added
OS/Version||All
Severity|critical
