"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "src/site/xdoc/manual/appenders.xml" between
apache-log4j-2.12.3-src.tar.gz and apache-log4j-2.12.4-src.tar.gz

About: Apache Log4j 2 is a logging library for Java. Source distribution (Java).
Caution: Release 2.12.3 is the last 2.x release to support Java 7 (Java 8 users should use 2.17.0 or greater) and have fixed a critical remote code execution vulnerability (CVE-2021-44228).

appenders.xml  (apache-log4j-2.12.3-src):appenders.xml  (apache-log4j-2.12.4-src)
skipping to change at line 985 skipping to change at line 985
<AppenderRef ref="eventLogger"/> <AppenderRef ref="eventLogger"/>
</Logger> </Logger>
<Root level="warn"> <Root level="warn">
<AppenderRef ref="STDOUT"/> <AppenderRef ref="STDOUT"/>
</Root> </Root>
</Loggers> </Loggers>
</Configuration>]]></pre> </Configuration>]]></pre>
</subsection> </subsection>
<a name="JDBCAppender"/> <a name="JDBCAppender"/>
<subsection name="JDBCAppender"> <subsection name="JDBCAppender">
<p>The JDBCAppender writes log events to a relational database table u <p>The JDBC Appender writes log events to a relational database table
sing standard JDBC. It can be configured using standard JDBC. It can be configured
to obtain JDBC connections using a JNDI <code>DataSource</code> or a to obtain JDBC connections using a JNDI <code>DataSource</code> or a
custom factory method. Whichever custom factory method.</p>
approach you take, it <strong><em>must</em></strong> be backed by a <p>The JDBC Appender configured with a <code>DataSource</code> require
connection pool. Otherwise, logging s JNDI support so as of release 2.17.1
this appender will not function unless <code>log4j2.enableJndiJdbc=t
rue</code> is configured as a system property
or environment variable. See the <a href="./configuration.html#enabl
eJndiJdbc">enableJndiJdbc</a> system property.</p>
<p>
Whichever approach you take, it <strong><em>must</em></strong> be ba
cked by a connection pool. Otherwise, logging
performance will suffer greatly. If batch statements are supported b y the configured JDBC driver and a performance will suffer greatly. If batch statements are supported b y the configured JDBC driver and a
<code>bufferSize</code> is configured to be a positive number, then log events will be batched. Note that as <code>bufferSize</code> is configured to be a positive number, then log events will be batched. Note that as
of Log4j 2.8, there are two ways to configure log event to column ma ppings: the original <code>ColumnConfig</code> of Log4j 2.8, there are two ways to configure log event to column ma ppings: the original <code>ColumnConfig</code>
style that only allows strings and timestamps, and the new <code>Col umnMapping</code> plugin that uses Log4j's style that only allows strings and timestamps, and the new <code>Col umnMapping</code> plugin that uses Log4j's
built-in type conversion to allow for more data types (this is the s ame plugin as in the built-in type conversion to allow for more data types (this is the s ame plugin as in the
<a href="#CassandraAppender">Cassandra Appender</a>).</p> <a href="#CassandraAppender">Cassandra Appender</a>).</p>
<p> <p>
To get off the ground quickly during development, an alternative to using a connection source based on To get off the ground quickly during development, an alternative to using a connection source based on
JNDI is to use the non-pooling <code>DriverManager</code> connection source. This connection source uses JNDI is to use the non-pooling <code>DriverManager</code> connection source. This connection source uses
a JDBC connection string, a user name, and a password. Optionally, y ou can also use properties. a JDBC connection string, a user name, and a password. Optionally, y ou can also use properties.
skipping to change at line 1530 skipping to change at line 1534
</Loggers> </Loggers>
</Configuration>]]></pre> </Configuration>]]></pre>
</subsection> </subsection>
<a name="JMSAppender"/> <a name="JMSAppender"/>
<!-- cool URLs don't change, so here are some old anchors --> <!-- cool URLs don't change, so here are some old anchors -->
<a name="JMSQueueAppender"/> <a name="JMSQueueAppender"/>
<a name="JMSTopicAppender"/> <a name="JMSTopicAppender"/>
<subsection name="JMS Appender"> <subsection name="JMS Appender">
<p>The JMS Appender sends the formatted log event to a JMS Destination .</p> <p>The JMS Appender sends the formatted log event to a JMS Destination .</p>
<p>The JMS Appender requires JNDI support so as of release 2.3.1 this appender will not function unless <p>The JMS Appender requires JNDI support so as of release 2.12.3 this appender will not function unless
<code>log4j2.enableJndiJms=true</code> is configured as a system pro perty or environment <code>log4j2.enableJndiJms=true</code> is configured as a system pro perty or environment
variable. See the <a href="./configuration.html#enableJndiJms">enabl eJndiJms</a> system property.</p> variable. See the <a href="./configuration.html#enableJndiJms">enabl eJndiJms</a> system property.</p>
<p> <p>
<p>
Note that in Log4j 2.0, this appender was split into a JMSQueueAppen der and a JMSTopicAppender. Starting Note that in Log4j 2.0, this appender was split into a JMSQueueAppen der and a JMSTopicAppender. Starting
in Log4j 2.1, these appenders were combined into the JMS Appender wh ich makes no distinction between queues in Log4j 2.1, these appenders were combined into the JMS Appender wh ich makes no distinction between queues
and topics. However, configurations written for 2.0 which use the <c ode>&lt;JMSQueue/&gt;</code> or and topics. However, configurations written for 2.0 which use the <c ode>&lt;JMSQueue/&gt;</code> or
<code>&lt;JMSTopic/&gt;</code> elements will continue to work with t he new <code>&lt;JMS/&gt;</code> <code>&lt;JMSTopic/&gt;</code> elements will continue to work with t he new <code>&lt;JMS/&gt;</code>
configuration element. configuration element.
</p> </p>
<table> <table>
<caption align="top">JMS Appender Parameters</caption> <caption align="top">JMS Appender Parameters</caption>
<tr> <tr>
<th>Parameter Name</th> <th>Parameter Name</th>
 End of changes. 3 change blocks. 
8 lines changed or deleted 14 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)