You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2012/03/09 21:13:04 UTC
DO NOT REPLY [Bug 52720] An incomplete fix for the resource leak
bugs in ManagerBase.java
https://issues.apache.org/bugzilla/show_bug.cgi?id=52720
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
OS/Version| |All
Severity|critical |enhancement
--- Comment #1 from Mark Thomas <ma...@apache.org> 2012-03-09 20:13:04 UTC ---
(In reply to comment #0)
> When the statements at lines 256 throw any eception,
If that happens, the container will have much bigger problems than a resource
leak.
> Besides that, when DataInputStream is created unsuccessfully but the temp
> FileInputStream object is created successfully at lines 250, the temp
> FileInputStream object will be leak.
Again, the type of exception that could trigger that to happen is going to
represent far bigger problems than a resource leak.
> The Same problem is also existed in the method of "setRandomFile".
See above.
There isn't anything here that is actually going to cause a problem for a user.
I am therefore dropping the severity to a realistic level.
These issues do not exist in later versions since the session ID generation has
been refactored.
Simply using a finally block will not achieve the desired outcome.
Given the extremely low chances of this ever happening and that for it to
happen something far worse has to go wrong (such as an OOME) I am resolving
this as WONTFIX.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org