Poor Logging Practice: Multiple Loggers - Revision history

MediaWiki spam cleanup: Reverting to last version not containing links to www.textallial.com

2009-05-27T18:29:03Z

Reverting to last version not containing links to www.textallial.com

Deleted user at 15:52, 22 May 2009

2009-05-22T15:52:30Z

KirstenS at 23:30, 7 April 2009

2009-04-07T23:30:17Z

KirstenS at 00:09, 18 February 2009

2009-02-18T00:09:32Z

KirstenS at 14:59, 5 November 2008

2008-11-05T14:59:41Z

KirstenS at 12:37, 30 September 2008

2008-09-30T12:37:10Z

Weilin Zhong: /* Description */

2006-07-21T16:00:48Z

‎Description

Weilin Zhong: /* Abstract */

2006-07-21T16:00:10Z

‎Abstract

Weilin Zhong at 15:57, 21 July 2006

2006-07-21T15:57:44Z

New page

{{Template:Vulnerability}}
{{Template:Fortify}}

==Abstract==

Use multiple loggers rather than logging levels in a single class.

==Description==

Good logging practice dictates the use of a single logger with different logging levels for each class.

==Examples ==

The following code errantly declares multiple loggers.

<pre>
public class MyClass {
private final static Logger good =
Logger.getLogger(MyClass.class);
private final static Logger bad =
Logger.getLogger(MyClass.class);
private final static Logger ugly =
Logger.getLogger(MyClass.class);
...
}

</pre>

==Related Threats==

==Related Attacks==

==Related Vulnerabilities==

==Related Countermeasures==

==Categories==

[[Category:Code Quality Vulnerability]]

[[Category:Logging and Auditing Vulnerability]]

[[Category:Java]]

[[Category:Implementation]]

[[Category:Code Snippet]]

← Older revision		Revision as of 18:29, 27 May 2009
Line 1:		Line 1:
−	~~http://www.textallial.com~~
	{{template:CandidateForDeletion}}		{{template:CandidateForDeletion}}

← Older revision		Revision as of 15:52, 22 May 2009
Line 1:		Line 1:
		+	http://www.textallial.com
	{{template:CandidateForDeletion}}		{{template:CandidateForDeletion}}

← Older revision		Revision as of 23:30, 7 April 2009
Line 4:		Line 4:


−	~~__TOC__~~
−
−	~~[[ASDR Table of Contents]]~~

	Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''		Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''

@@ Line 1: / Line 1: @@
-{{Template:Vulnerability}}
+{{template:CandidateForDeletion}}
-{{Template:Fortify}}
 __TOC__
@@ Line 7: / Line 9: @@
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 ==Description==
@@ Line 75: / Line 73: @@
 __NOTOC__

@@ Line 1: / Line 1: @@
 {{Template:Fortify}}
-[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+__TOC__
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
-[[ASDR Table of Contents]]
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
@@ Line 72: / Line 72: @@
 * [http://www.link2.com Title for the link2]
 __NOTOC__
@@ Line 107: / Line 83: @@
 [[Category:Implementation]]
 [[Category:Code Snippet]]

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
-==Abstract==
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 ==Description==
 Good logging practice dictates the use of a single logger that supports different logging levels for each class.
 ==Examples ==
 The following code errantly declares multiple loggers.
@@ Line 27: / Line 41: @@
 </pre>
-==Related Attacks==
+==Related [[Attacks]]==
-==Related Vulnerabilities==
+Session Management Vulnerability]]
-==Related Countermeasures==
+__NOTOC__
 [[Category:Code Quality Vulnerability]]
 [[Category:Logging and Auditing Vulnerability]]
 [[Category:Java]]
 [[Category:Implementation]]
 [[Category:Code Snippet]]

@@ Line 4: / Line 4: @@
 ==Abstract==
-Use multiple loggers rather than logging levels in a single class.
+It is a poor logging practice to use multiple loggers rather than logging levels in a single class.
 ==Description==