[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bugs #8921] LogManager.findAncestor throws exception if a logger has be
From: |
anonymous |
Subject: |
[bugs #8921] LogManager.findAncestor throws exception if a logger has been garbage collected |
Date: |
Wed, 12 May 2004 17:47:40 -0400 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 |
This mail is an automated notification from the bugs tracker
of the project: classpath.
/**************************************************************************/
[bugs #8921] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=8921>
Project: classpath
Submitted by: 0
On: Wed 05/12/04 at 21:45
Severity: 5 - Average
Resolution: None
Assigned to: None
Status: Open
Platform Version: None
Summary: LogManager.findAncestor throws exception if a logger has been garbage
collected
Original Submission: Because the LogManager maintains a copy of all loggers as
weak references, loggers can be garbage collected.
This means that if a logger is GC'd, the next time the logger is looked up (via
Logger.getLogger), an ArrayIndexOutOfBounds exception will be thrown in the
charAt(candNameLength) statement, because candName and child will reference the
same logger [at some point], thus candNameLength == childName.length(),
therefore, childName.charAt(candNameLength) is out of bounds.
For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=8921>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bugs #8921] LogManager.findAncestor throws exception if a logger has been garbage collected,
anonymous <=