History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: SDK-15562
Type: Bug Bug
Status: Community Community
Priority: None None
Assignee: Joan Lafferty
Reporter: Jürgen Failenschmid
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Flex SDK

AbstractTarget#set level() does not check if there are any loggers, causing the logger count to be wrong

Created: 05/13/08 06:48 PM   Updated: 05/13/08 06:48 PM
Component/s: Unspecified - App Model
Security Level: Public (All JIRA Users )

Severity: Incorrectly Functioning with Workaround
Reproducibility: Every Time
Discoverability: Medium
Found in Version: SDK Flex 3 (Released)
Affected OS(s): All OS Platforms
Steps to Reproduce:
mx.logging.AbstractTarget#set level() calls Log#removeTarget() without first checking if there are any loggers. Then #removeLogger() does not check if the logger count is zero, thereby setting the logger count to -1.
Once #set level exits, the loggerCount is zero, although a listener was added.

Compare with AbstractTarget#set filters(), which first checks if there are any loggers.

The logger count must be in sync with the number of event listeners added to the logger, otherwise strange things happen, such as duplicate log entries, although only one logger is active.

Workaround (if any):

Calling Log.addTarget(target) before setting the target's level avoids the problem of setting the logger count to -1.
Language Found: English
Bugbase Id: none
QA Owner: Joan Lafferty
Participants: Joan Lafferty and Jürgen Failenschmid


 All   Comments      Sort Order:
There are no comments yet on this issue.