StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12578514
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-25T07:54:09.373
FavoriteCount
0
LastActivityDate
2012-09-25T07:54:09.373
LastEditDate
LastEditorUserId
0
OwnerUserId
1350983
ParentId
12536960
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The NullAppender basically does nothing, like others have already pointed out. I just wanted to layout some details. <pre> AppenderSkeleton implements Appender { ... @Override public synchronized void doAppend(LoggingEvent event) { ... } ... abstract protected void append(LoggingEvent event); } public class NullAppender extends AppenderSkeleton { public static String s; public String t; ... @Override public void doAppend(LoggingEvent event) { if(layout != null) { t = layout.format(event); s = t; } } @Override public void append(LoggingEvent event) { } </pre> See also: <a href="http://javasourcecode.org/html/open-source/log4j/log4j-1.2.8/org/apache/log4j/performance/NullAppender.java.html#line.48" rel="nofollow">Source-NullAppender</a> & <a href="http://javasourcecode.org/html/open-source/log4j/log4j-1.2.8/org/apache/log4j/AppenderSkeleton.java.html" rel="nofollow">Source-AppenderSkeleton</a> What happens at each and every log.trace/debug/... call is <pre> -> org.apache.log4j.Category.forcedLog(String fqcn, Priority level, Object message, Throwable t) -> org.apache.log4j.Category.callAppenders(LoggingEvent event) -> org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(LoggingEvent event) is called on each Appender within that Logger -> org.apache.log4j.Appender.doAppend(LoggingEvent event) which is NullPointers implementation of doAppend in this case. </pre> As you see, the NullAppender takes away the synchronization, NullAppender.doAppend produces some overhead, but it is very little in most scenarios. As for JDBCAppender it should not be used. <pre> WARNING: This version of JDBCAppender is very likely to be completely replaced in the future. Moreoever, it does not log exceptions. </pre> See: <a href="http://www.docjar.com/html/api/org/apache/log4j/jdbc/JDBCAppender.java.html" rel="nofollow">JDBC-Appender-Source</a> Line 34-36 As an alternative you might want to check out <a href="http://www.clusterlog.net" rel="nofollow">clusterlog</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAbout log4j.xml NullAppender
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSebastian van Wickern
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.