Ralph Goers | 11 Dec 01:51 2015

[ANNOUNCEMENT] Apache Log4j 2.5 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.5 release!


Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to

Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides

many other modern features such as support for Markers, property substitution using Lookups, multiple patterns on

a PatternLayout and asynchronous Loggers. In addition, Log4j 2 will not lose events while reconfiguring.


This is the ninth GA release. It contains several bugfixes and new features. The new features include

the ability to specify delete actions during file rollover, a CRON-based triggering policy for file rollover,

Support for JSR 223 scripts in filters, pattern selectors and delete actions, and a policy for removing

idle appenders from the RoutingAppender. More details on the features and bugfixes are itemized below.


Log4j 2 requires a minimum of Java 7.


GA Release 2.5


Changes in this version include:


New features:

o LOG4J2-435:  Added support for custom delete actions triggered by a rollover. Thanks to Robert Schaft.

o LOG4J2-89:  Allow rollover to occur at any time. Add CronTriggeringPolicy.

o LOG4J2-1136:  Add support for JSR 223 scripts in filters and the PatternSelector.

o LOG4J2-1168:  Add getters for source and destination file in file rename action. Thanks to Steven Swor.

o LOG4J2-1175:  Add getters for classes in org.apache.logging.log4j.core.appender.rolling.action.

o LOG4J2-898:  Added system property to allow users to control whether messages should be formatted in the background.

o LOG4J2-1178:  Support use-case for JDBC's CommonDataSource.setLogWriter(PrintWriter) and java.sql.DriverManager.setLogWriter(PrintWriter).

o LOG4J2-1187:  Support use case for java.sql.DriverManager.setLogStream(PrintStream).


Fixed Bugs:

o LOG4J2-324:  Reduced memory usage of status messages in bounded queue; support zero-length queue that stores no messages.

o LOG4J2-1173:  Fixed rollover error when copying to a directory mapped to a remote Linux host.

o LOG4J2-1195:  Make KafkaAppender support SerializedLayout. Thanks to Melvin Du.

o LOG4J2-381:  Allow triggering policy and rollover strategy to be modified during reconfiguration. Thanks to Anthony Baldocchi.

o LOG4J2-1029:  Performance improvement when gathering location information. Thanks to Stefan Leonhartsberger.

o LOG4J2-1172:  Fixed ThreadLocal leak [AsyncLogger$Info] on Tomcat when using AsyncLoggerContextSelector.

o LOG4J2-1176:  Fixed memory leak when log4j jars are in Tomcat's lib folder.

o LOG4J2-1180:  Logger cache does not account for message factory. Thanks to Mikael Ståldal.

o LOG4J2-879:  Documentation: fixed minor issues with the site and manual pages.

o LOG4J2-999:  RollingFileAppender should also roll over when log event time is equal to rollover time, not only when later. Thanks to Joan Balagueró.

o LOG4J2-873:  Fixed bug where omitting the <display-name> element in web.xml caused incorrect log4j initialization,

        resulting in memory leaks when the web application was stopped or reloaded. Thanks to Martin Dickins, LC, Luke Woodward.

o LOG4J2-323:  Better web app support for async loggers: Fixed a memory leak that occurred when the logging jars are placed

        in the container's classpath and the configuration file uses AsyncRoot/AsyncLogger.

        The problem was that the first web application started the Disruptor background thread [AsyncLoggerConfig-1] but did not stop it until all web apps are stopped.

        Each web application now has its own Disruptor which is stopped/started together with the web app.

o LOG4J2-493:  Better web app support for async loggers: it is now possible to place the logging jars in the container's

        classpath when making all loggers asynchronous by using AsyncLoggerContextSelector. This fixes a problem where

        logging would stop working after stopping and restarting a web application.

o LOG4J2-1171:  Use servlet context name for logger context name when available.

o LOG4J2-1159:  Fixed a ThreadLocal memory leak in Tomcat8 that mentions AsyncLoggers when Async Loggers are not used.

o LOG4J2-1166:  AbstractConfiguration executor should use a DaemonThreadFactory.

o LOG4J2-1165:  Improve Log4j initialization status messages.

o LOG4J2-1156:  Web site corrections and updates.

o LOG4J2-1158:  Log4J JUL adapter is using MessageFormat on String passed by java.util.function.Supplier<String>. Thanks to Michael Fortin, Gary Gregory.

o LOG4J2-801:  org.apache.logging.log4j.core.Logger should be serializable.

o LOG4J2-1157:  Fix compilation error for classes annotated with <at> Plugin. Thanks to Norbert Bartels.

o LOG4J2-948:  Fix plugin documentation error about Converters. Thanks to Andrew Flower.

o LOG4J2-1193:  Prefix all thread names Log4j creates with "Log4j2-".

o LOG4J2-1194:  Documentation does not match parameters for LoggerNameLevelRewritePolicy. Thanks to Adam Brin.

o LOG4J2-1196:  MongoDbConnection does not close MongoClient. Thanks to René Zanner.


Changes:

o LOG4J2-649:  Add PurgePolicy and IdlePurgePolicy to RoutingAppender. Thanks to Aleksey Zvolinsky.

o LOG4J2-1202:  Remove ConfigurationMonitor. The WatchManager is now used to check for configuration changes.

o LOG4J2-1174:  Update Jackson from 2.6.2 to 2.6.3.

o LOG4J2-1207:  Update kafka-clients from 0.8.2.2 to 0.9.0.0.



Apache Log4j 2.5 requires a minimum of Java 7 to build and run. Log4j 2.3 was the last release that

supported Java 6.


Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api component, however it does not implement some of the

very implementation specific classes and methods. The package names and Maven groupId have been changed to

org.apache.logging.log4j to avoid any conflicts with log4j 1.x.


For complete information on Apache Log4j 2, including instructions on how to submit bug reports,

patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:


http://logging.apache.org/log4j/2.x/


Stefan Bodewig | 10 Dec 06:30 2015
Picon
Gravatar

[ANN] Apache log4net 1.2.15 Released


The Apache log4net team is pleased to announce the release of Apache
log4net 1.2.15.  The release is available for download at

        http://logging.apache.org/log4net/download_log4net.cgi

The Apache log4net library is a tool to help the programmer output log
statements to a variety of output targets.  log4net is a port of the
excellent Apache log4j framework to the Microsoft(R) .NET runtime.

This is the last log4net release that provides assemblies for .NET 1.x
or 2.0 and Mono 1.x.  We intend to stay compatible with those
frameworks in future releases but people using said frameworks will
need to build the binaries from the source distribution themselves.

People using said frameworks should notice that they will eventually
have to maintain compatibility in the rare case that future
modifications to log4net broke the compatibility. Patches are always
welcome! We decided to take this step because supporting these old
frameworks consumes a large amount of resources while the effort is
probably wasted.

See the release-notes at

    http://logging.apache.org/log4net/release/release-notes.html

for a full list of changes.

Please verify signatures using the KEYS file available at the above
location when downloading the release.

For complete information on log4net, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the
Apache log4net website:

        http://logging.apache.org/log4net/

Apache Wiki | 7 Dec 00:54 2015
Picon

[Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Logging Wiki" for change notification.

The "Log4j2ReleaseGuide" page has been changed by RalphGoers:
https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=37&rev2=38

   1. Run {{{mvn -P release-notes generate-resources}}} to create the release notes.
   1. Update {{{src/changes/changes.xml}}} with the release date.
   1. Run {{{git add, git commit, and git push}}} to commit the {{{RELEASE-NOTES.txt}}} file that was just generated.
-  1. Run {{{mvn -P apache-release release:prepare release:perform -DreleaseVersion=n.n
-DdevelopmentVersion=n.n-SNAPSHOT}}} to start the release. Enter the password to your signing key
when prompted.
+  1. Run {{{mvn -P apache-release release:prepare release:perform -DreleaseVersion=n.n
-DdevelopmentVersion=n.n-SNAPSHOT -Dtag=log4j-n.n-rcn}}} to start the release. Enter the password
to your signing key when prompted.
   1. Login to http://repository.apache.org using your ASF credentials. Select "Staging Repositories"
then check the {{{org.apache.logging}}} repository and close it.
   1. Check out the release tag that was created via the Maven release plugin using {{{git checkout tags/tagname}}}.
   1. Run {{{mvn site}}} in the tag directory. When that completes run {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
 <at>  <at>  -64, +64  <at>  <at> 

      a. Provide the command to download all the artifacts: {{{wget -e robots=off --cut-dirs=3 -r -p -np
--no-check-certificate $LINK}}} where {{{$LINK}}} is the URL to the repository you just closed (plus
the {{{org/apache/logging/log4j/}}} path appended).
      a. Provide a list of the artifacts by copying from the email notification sent from the Nexus
Repository.<<FootNote(Nexus has not been sending this email for the past few releases at least)>>
   1. If the release vote fails proceed as described in the section below, otherwise if it passes:
+     a. Create a new tag named log4j-n.n from the log4j-n.n-rcn tag.
      a. Download all the distribution files from the Nexus repository (you can download using the wget above and
then going to the distribution sub-directory).
      a. Rename the distribution files back to their original names (Maven renamed them when they were deployed
to Nexus) using {{{for f in log4j-distribution-*; do mv $f $(echo $f | sed
's/^log4j-distribution-/apache-log4j-/g'); done}}}
      a. Delete the {{{*.asc.md5}}} and {{{*.asc.sha1}}} files and {{{*.pom*}}}.

Stefan Bodewig | 6 Dec 06:29 2015
Picon
Gravatar

[VOTE] Release log4net 1.2.15 Based on RC1


Hi

with 1.2.14 we've introduced a serious regression inside the ADO.NET
appender - also we seem to have missed a few crucial patches needed to
make async/await supported properly.  Therefore a new release is
warranted.

log4net 1.2.15 RC1 is available for review here:
  https://dist.apache.org/repos/dist/dev/logging/log4net
    (revision 11436)

Details of changes since 1.2.15 are in the release notes:
  http://home.apache.org/~bodewig/log4net-1.2.15/site/release/release-notes.html

I have tested this with Mono and several .NET frameworks using NAnt.

The tag is here:
  https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.15RC1
    (revision 1717718)

Site:
  http://home.apache.org/~bodewig/log4net-1.2.15/

RAT Report:
  http://home.apache.org/~bodewig/log4net-1.2.15/rat-report.html

Votes, please.  This vote will close in 72 hours, 0530 GMT 9-Dec 2015

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...

Thanks! 
Roman Shaposhnik | 1 Dec 07:30 2015
Picon
Gravatar

FOSDEM 2016 - take action by 4th of December 2015

As most of you probably know FOSDEM 2016 (the biggest,
100% free open source developer conference) is right 
around the corner:
   https://fosdem.org/2016/

We hope to have an ASF booth and we would love to see as
many ASF projects as possible present at various tracks
(AKA Developer rooms):
   https://fosdem.org/2016/schedule/#devrooms

This year, for the first time, we are running a dedicated
Big Data and HPC Developer Room and given how much of that
open source development is done at ASF it would be great
to have folks submit talks to:
   https://hpc-bigdata-fosdem16.github.io

While the CFPs for different Developer Rooms follow slightly 
different schedules, but if you submit by the end of this week 
you should be fine.

Finally if you don't want to fish for CFP submission URL,
here it is:
   https://fosdem.org/submit

If you have any questions -- please email me *directly* and
hope to see as many of you as possible in two months! 

Thanks,
Roman.

Rich Bowen | 25 Nov 18:32 2015
Gravatar

[ANNOUNCE] CFP open for ApacheCon North America 2016

Community growth starts by talking with those interested in your
project. ApacheCon North America is coming, are you?

We are delighted to announce that the Call For Presentations (CFP) is
now open for ApacheCon North America. You can submit your proposed
sessions at
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
for big data talks and
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
for all other topics.

ApacheCon North America will be held in Vancouver, Canada, May 9-13th
2016. ApacheCon has been running every year since 2000, and is the place
to build your project communities.

While we will consider individual talks we prefer to see related
sessions that are likely to draw users and community members. When
submitting your talk work with your project community and with related
communities to come up with a full program that will walk attendees
through the basics and on into mastery of your project in example use
cases. Content that introduces what's new in your latest release is also
of particular interest, especially when it builds upon existing well
know application models. The goal should be to showcase your project in
ways that will attract participants and encourage engagement in your
community, Please remember to involve your whole project community (user
and dev lists) when building content. This is your chance to create a
project specific event within the broader ApacheCon conference.

Content at ApacheCon North America will be cross-promoted as
mini-conferences, such as ApacheCon Big Data, and ApacheCon Mobile, so
be sure to indicate which larger category your proposed sessions fit into.

Finally, please plan to attend ApacheCon, even if you're not proposing a
talk. The biggest value of the event is community building, and we count
on you to make it a place where your project community is likely to
congregate, not just for the technical content in sessions, but for
hackathons, project summits, and good old fashioned face-to-face networking.

--

-- 
rbowen <at> apache.org
http://apache.org/

Christian Grobmeier | 20 Nov 16:33 2015
Picon
Gravatar

[ANNOUNCEMENT] Welcome Ralph Goers as the new Apache Logging Chair

Hello all,

I was the chair of the Apache Logging Services project for 3 1/2 years.
Thank you, it was a great time. But it is time to move on. I think it is
critical for ASF projects to let the Chair role rotate. 

At Logging Services, we agreed to discuss the role each year at the time
of the ASF members meeting. We did that. We will continue to do that (at
least that's my hope! :)).

The PMC discussed who could fill the role of the Logging Chair, and
while we have many great people among us, we unanimously voted for Ralph
Goers.

Ralph wrote the first versions of what became Log4j 2.0. He wrote large
parts of it until a fantastic community grew around the project. Without
him and his hard work, we would still be stuck on Log4j 1.x times when
things didn't look so bright. 
Ralph is not only an experienced developer but also a great teammate and
knows the Apache way in and out. 

Now I am very happy to say he accepted our vote, and the ASF Board
confirmed him in his role, effective immediately.

Welcome, Ralph! All the best for your new role, and may the force be
with you!

Cheers,
Christian

PS: if you are confused by the terms PMC, Chair or whatever, I'd like to
invite you to read the blog I posted when I became chair:
http://www.grobmeier.de/hey-i-became-a-vice-president-07072012.html

Or the official docs:
http://www.apache.org/foundation/how-it-works.html

Stefan Bodewig | 11 Nov 13:12 2015
Picon
Gravatar

[ANN] Apache log4net 1.2.14 Released


The Apache log4net team is pleased to announce the release of Apache
log4net 1.2.14.  The release is available for download at

        http://logging.apache.org/log4net/download.html

The Apache log4net library is a tool to help the programmer output log
statements to a variety of output targets.  log4net is a port of the
excellent Apache log4j framework to the Microsoft(R) .NET runtime.

The log4net 1.2.14 release fixes a problem with logical thread
properties used together with async/await as well as a bugs.  It also
adds a new option to SmtpPickupDirAppender.

See the release-notes at

    http://logging.apache.org/log4net/release/release-notes.html

for a full list of changes.

Please verify signatures using the KEYS file available at the above
location when downloading the release.

For complete information on log4net, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the
Apache log4net website:
Stefan Bodewig | 7 Nov 17:32 2015
Picon
Gravatar

[VOTE] Release log4net 1.2.14 based on RC2


log4net 1.2.14 RC2 is available for review here:
  https://dist.apache.org/repos/dist/dev/logging/log4net
    (revision 11058)

Details of changes since 1.2.14 are in the release notes:
  http://people.apache.org/~bodewig/log4net/site/release/release-notes.html

The tag is here:
  https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.14RC2
    (revision 1713091)

Site:
  http://people.apache.org/~bodewig/log4net/site/

Votes, please.  This vote will closeno sooner than in 72 hours, 1630 GMT
10-Nov 2015

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...

Thanks!
Stefan Bodewig | 18 Oct 08:20 2015
Picon
Gravatar

[VOTE] Release Apache log4net 1.2.14 based on RC1

log4net 1.2.14 RC1 is available for review here:
  https://dist.apache.org/repos/dist/dev/logging/log4net
  (revision 10847)

Details of changes since 1.2.13 are in the release notes:
  http://people.apache.org/~bodewig/log4net/site/release/release-notes.html

The tag is here:
  https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.14RC1
  (revision 1709237)

Site:
  http://people.apache.org/~bodewig/log4net/site/

will need to get adapted to mention support for 4.5, this can happen
during the time frame of the vote.

Votes, please.  This vote will close in 72 hours, not before 0700 GMT
21-Oct 2015

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...

Ralph Goers | 13 Oct 16:00 2015

[ANNOUNCEMENT] Apache Log4j 2.4.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.4.1 release!

Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides
many other modern features such as support for Markers, property substitution using Lookups, and asynchronous
Loggers. In addition, Log4j 2 will not lose events while reconfiguring.

This is the ninth GA release. It contains several bugfixes and new features.
Log4j 2 requires a minimum of Java 7.

GA Release 2.4.1

Changes in this version include:

New features:
o LOG4J2-1129: Allow PatternLayout to select a pattern to use based on some selection criteria.
o LOG4J2-1145: Add %equals to PatternLayout to test and replace patterns with strings.
o LOG4J2-1147: Add %equalsIgnoreCase to PatternLayout to test and replace patterns with strings.
o LOG4J2-1146: Add %notEmpty to PatternLayout to avoid output of patterns where all variables are empty.
o LOG4J2-1020: Add possibility to set shutdown timeout on AsyncAppender.

Fixed Bugs:
o LOG4J2-1153: Fixed NullPointerException when only root logger is defined (and no named loggers) in configuration properties file.
o LOG4J2-1140: Fixed bug where headers were not being written to first file with RollingFileAppender.
o LOG4J2-1149: Fixed bug where PatternLayout predefined date pattern with time zone always renders default date format.
o LOG4J2-1050: Fixed Log4jLookup.
o LOG4J2-1142: Fix potential memory leak in web applications by using a straight ThreadLocal field instead of subclassing ThreadLocal.
o LOG4J2-1135: Compression on rollover was broken: log file was renamed to .zip but not compressed.
o LOG4J2-1127: log4j2.xml cannot be parsed on Oracle Weblogic 12c.
o LOG4J2-1132: Do not use MongoDB driver 2.13.3 deprecated methods.
o LOG4J2-1144: Add %markerSimpleName in pattern layout should evaluate to marker name (not toString()).
o LOG4J2-1126: Web site corrections and updates.

Changes:
o LOG4J2-1151: Performance improvement: backport Java 8 fast ISO-8859-1 String to byte[] encoder to AbstractStringLayout.
o LOG4J2-935: Performance improvement when converting Strings to byte[] arrays.
o LOG4J2-1040: Update MongoDB driver from 2.13.3 to 3.0.4.
o LOG4J2-1128: Reuse StringBuilder to improve performance for String-based layouts: CSV, GELF, HTML, RFC524, Syslog.
o LOG4J2-1131: Update mongo-java-driver from 2.13.2 to 2.13.3.
o LOG4J2-1138: Do not use Jackson deprecated methods.
o LOG4J2-1139: Update Jackson from 2.6.1 to 2.6.2.
o LOG4J2-1150: Update kafka-clients from 0.8.2.1 to 0.8.2.2.


Apache Log4j 2.4.1 requires a minimum of Java 7 to build and run. Log4j 2.4 and greater requires Java 7,
version 2.3 required Java 6.

Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api component, however it does not implement some of the
very implementation specific classes and methods. The package names and Maven groupId have been changed to
org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:

http://logging.apache.org/log4j/2.x/

Gmane