Ralph Goers | 12 May 2013 08:09
Favicon

[ANNOUNCEMENT] Apache Log4j 2.0-beta6 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta6 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 of the improvements available in Logback while fixing some inherent problems in Logback's
architecture.

This is the eighth release of Log4j 2 and is being made available to encourage use and feedback from the community.

Bug fixes and enhancements

Changes in this version include:

Fixed Bugs:
o LOG4J2-231:  Logger.getParent() was not returning the correct Logger. 
o LOG4J2-201:  Renamed Plugin annotation attribute from "type" to "category". 
o LOG4J2-219:  Fix: install default root logger if not configured (this is unchanged),
        but make sure to include configured named loggers. Clarified documentation. Thanks to Peter DePasquale. 
o LOG4J2-159:  Use OSGi version format in Fragment-Host 
o LOG4J2-234:  RegexFilter threw a NullPointerException when used as a context-wide filter. 
o LOG4J2-192:  Add support for interpolating Environment variables when processing the configuration. 
o LOG4J2-235:  Removed dependency on tools jar from core module, made jconsole dependency optional.
Thanks to Sebastian Oerding. 
o LOG4J2-233:  Fixed link to log4j-user mailing list. 
o LOG4J2-222:  Disruptor will now shutdown during Tomcat shutdown. Thanks to Steven Yang. 
o LOG4J2-224:  The FlumeAppender failed to start if the Flume RPCClient could not connect to any Flume
agents. 
o LOG4J2-223:  Fix LoggerContext start and stop to eliminate IllegalStateException and NoClassDefFound
errors. 
o LOG4J2-221:  Remove hundreds of compiler warnings. Thanks to Nick Williams. 
(Continue reading)

Christian Grobmeier | 3 May 2013 11:19
Picon
Gravatar

log4cx: attic or incubation?

Hello folks,

please look at these few e-mails:
http://mail-archives.apache.org/mod_mbox/logging-log4cxx-dev/201304.mbox/browser

For me there are two ways for log4cxx: incubation or attic.

I was outreaching for devs on log4cxx and got a few responses. It seems a couple
of people are interested in continuing this component. Most of them
said they might apply a couple of patches here and there, but nobody
burst out in emotions saying, YAY, this is it.

Without such a person I guess we have little chance in the incubator.
Maybe I am having a wrong view on it, so I ask you to voice your
opinion.

For now I would like to propose that I am cloning log4cxx to my GitHub
account and move the svn repos to the attic. That way I can overlook
if there is a team growing around log4cxx or not. Also I can ask for
ICLAs before accepting pull requests, which should help when we go
back to incubation. If there is, we can go back to incubation at any
time. If there is not, then well, no harm done.

Comments?

Christian

--
http://www.grobmeier.de
https://www.timeandbill.de
(Continue reading)

Ralph Goers | 25 Apr 2013 08:17
Favicon

[ANNOUNCEMENT] Apache Log4j 2.0-beta5 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta5 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 of the improvements available in Logback while fixing some inherent problems in Logback's
architecture.

This is the seventh release of Log4j 2 and is being made available to encourage use and feedback from the community.

Bug fixes and enhancements

Changes in this version include:

New features:
o LOG4J2-207:  Add JMX support. Thanks to Remko Popma. 
o LOG4J2-187:  Add tag library. Thanks to Nick Williams. 
o LOG4J2-164:  Add methods is/setEndOfBatch to LogEvent. Thanks to Remko Popma. 
o LOG4J2-163:  Add support for asynchronous loggers. Thanks to Remko Popma. 
o LOG4J2-179:  Add Logger interface APIs to log at given levels. 
o Added FlumePersistentManager which writes to BerkeleyDB and then writes to Flume asynchronously. 
o LOG4J2-155:  Expose file appender configuration details via an advertisement mechanism. 

Fixed Bugs:
o LOG4J2-205:  Fix deadlock in SocketAppender. Added option to not wait for socket reconnect. 
o LOG4J2-211:  Removing extra spaces in entry and exit method output. Thanks to Nick Williams. 
o LOG4J2-212:  Loggers without a "." had no parent logger. 
o LOG4J2-212:  Call LoggerContext.stop when the application is shutdown. 
o LOG4J2-210:  MapMessage was not enclosing key value in quotes when generating XML. Thanks to Arkin Yetis. 
o LOG4J2-198:  FlumeAvroManager now uses Flume RPCClient. 
o LOG4J2-196:  FlumeAvroManager now uses Flume RPCClient. 
(Continue reading)

Andrus Adamchik | 18 Mar 2013 13:09
Picon
Favicon

Mirroring Log4J 2 on GitHub

Hey guys,

There's a Log4J mirror on GitHub at https://github.com/apache/log4j . Would it be possible to also mirror
Log4J2? 

We've recently switched to Log4J2 on one of the big projects that I am doing. Now we need to patch a few things
for our work in a way that is likely not going to be accepted back to Log4J. Specifically we want to
short-circuit Log4jLogEvent.getSource to return a fixed String. We are using AsynchAppender and
'Log4jLogEvent.getSource' is a noticeable performance bottleneck for us, and we currently don't see a
better way around it (ok, to be completely honest, we just don't have the cycles to refactor Log4J2
properly). So the idea was to keep a GitHub fork and merge periodically with the master copy.

Any thoughts/comments on exposing "2" on GitHub. 

As an Apache member I can probably ping infra myself. But wanted to talk to the 'logging' community first.

Thanks,
Andrus
Dominik Psenner | 25 Feb 2013 11:52
Picon
Gravatar

Daily gump builds

Hey,

Is there an easy way to get my hands on the daily builds gump does for us? Maybe there is a documentation
somewhere that i haven't
found? Until now I crawled myself through here:

http://vmgump.apache.org/gump/public/index.html

without success.

Cheers,
Dominik

Christian Grobmeier | 7 Feb 2013 06:31
Picon
Gravatar

Moving log4cxx to the Attic

Hello

I would like to propose we move the log4cxx component to the attic.
I am not sure if the Apache Attic itself is the right place:
http://attic.apache.org/

as it seems to feed on TLDs only. I will ask there, if we agree that
log4cxx is not really maintained and that there will no work happen in
future.

I have hoped that there were a couple of people coming back to the
project when they see somebody is committing their patches. But it
hasn't happened and my own C skills are not enough to push this (time
is an issue too).

In case we agree, I would like to to keep the old log4cxx website,
saying this project is not longer maintained and the source code has
been moved to attic (if the attic.apache.org would take it). Other
options are also welcome, just let me hear what you think.

Best regards,
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

Ralph Goers | 1 Feb 2013 17:15
Favicon

[ANNOUNCEMENT] Apache Log4j 2.0.beta4 released

The Apache Logging team is pleased to announce the Apache log4j 2.0-beta4 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 of the improvements available in Logback while fixing some inherent problems in Logback's 
architecture.

This is the sixth release of Log4j 2 and is being made available to encourage use and feedback from the community\\

Changes in this version include:

New features:
o Added Log4j 2 to SLF4J adapter. 
o LOG4J2-131:  Add SMTPAppender. Thanks to Scott Severtson. 
o Added hostName and contextName to property map. 
o Add MessageFormatMessage and FormattedMessage. 
o LOG4J2-134:  Use %red, %white, %blue, and so on in the console appender. 
o LOG4J2-133:  Allow custom message creation via a message factory. 
o Added Flume Appender samples. 

Fixed Bugs:
o LOG4J2-156:  LocalizedMessageTest fails on linux system. Thanks to Andreas Born. 
o LOG4J2-152:  RollingFileAppender's FileRenameAction was throwing a NullPointerException if no directory was specified
        on the target file name. Thanks to Remko Popma. 
o LOG4J2-150:  Convert all System.getProperty calls to use PropertiesUtil to suppress SecurityExceptions. 
o LOG4J2-147:  ThreadContextMapFilter was matching on the key instead of the value of the key. Thanks to William Burns. 
o Allow FlumeAvroManager to initialize even if it cannot connect to an agent. 
o LOG4J2-149:  SMTPAppender will only cache filtered events. Thanks to Scott Severtson. 
o LOG4J2-145:  Add missing serial version IDs. 
o LOG4J2-144:  NullPointerException in RFC5424Layout. 
o LOG4J2-143:  MessagePatternConverter now returns "null" if the log message is null. 
o LOG4J2-142:  Serialized LogEvents were not reset in the output stream causing them to deserialize incorrectly. 
o LOG4J2-139:  Fix null pointer exception in SocketAppender if no protocol is specified. The protocol will default
        to TCP for the SocketAppender and UDP for the SyslogAppender. 
o LOG4J2-140:  Typo in documentation of SocketAppender. Thanks to Joern Huxhorn. 
o LOG4J2-137:  Fix hang in Dumbster SMTP test server. 
o LOG4J2-130:  PatternLayout should format throwables without requiring a converter. 
o LOG4J2-135:  BaseConfiguration does not close the first appender. Thanks to Ingo Feltes. 
o LOG4J2-132:  AbstractLogger.catching(Throwable) checks for DEBUG level but logs at ERROR level. 
o LOG4J2-129:  RoutingAppender was only creating a single appender for the default Route. 
o LOG4J2-126:  Allow JMS appenders to recover if the queue or topic is unavailable. 
o LOG4J2-127:  AbstractLogger methods were not passing Markers to the isEnabled methods. 
o LOG4J2-125:  JMSQueue and JMSTopic Appenders did not allow name to be specified. 
o LOG4J2-111:  Enhanced javadoc copyright statement. 
o LOG4J2-120:  TCPSocketManager would fail if the initial connection could not be established. 
o LOG4J2-119:  A broken socket connection would cause the TCPSocketManager to continuously reconnect. 
o LOG4J2-123:  The example for ThreadContextMapFilter was incorrect. Thanks to Olivier Lamy. 
o LOG4J2-116:  File renaming was using the wrong date value. Enhanced DefaultRolloverStrategy to store newest files in
        highest index as well as lowest. 
o LOG4J2-115:  ThreadContext Map elements with null values are now ignored when constructing a Flume event and in the
        RFC5424 Layout. 
o LOG4J2-113:  StructuredDataFilter createFilter was annotated with PluginAttr instead of PluginElement for the
        KeyValuePairs. 
o LOG4J2-114:  StructuredDataMessage was validating the length of the values in the event Map instead of the lengths
        of the keys. Thanks to Arkin Yetis. 

Changes:
o LOG4J2-136:  Allow newlines to be escaped in Syslog and RFC5424 layouts. Allow Throwables to be included in
        the output from RFC5424Layout. Thanks to Scott Severtson. 
o LOG4J2-128:  Add follow attribute to Console Appender. 
o LOG4J2-122:  Add unit test to verify exceptions are thrown when the socket connection fails. 
o LOG4J2-110:  Renamed log4j12-api to log4j-1.2-api. 

Apache Log4j 2.0-beta4 requires a minimum of Java 5 to build and run. Basic compatibility with
Log4j 1.x is provided through the log4j12-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:

Ralph Goers | 31 Jan 2013 19:00
Favicon

Distribution directories

As part of the release of Log4j 2.0-beta4 I copied all the current release artifacts from http://www.apache.org/dist/logging/to https://dist.apache.org/repos/dist/release/logging/.  Any future releases should be published through this location in subversion instead of the prior location via people.apache.org.

Ralph
Timur Nurlygayanov | 7 Jan 2013 15:40
Gravatar

How to log to the Data Base

Hi all,

I new user of log4j and I want to store my logs into the Data Base (like MySQL), but looks like I can't do this with new beta version of the library log4j2.

Probably you can send link or instruction how I can do this.


Regards,
Timur Nurlygayanov
Christian Grobmeier | 2 Jan 2013 11:25
Picon
Gravatar

Please update your fingerprints on id

Hello folks,

if you are not listed here:
http://people.apache.org/keys/group/logging-pmc.asc

its time to go to id.apache.org and add your fingerprint. You'll then
appear in the file after a while.

Today I was looking at an issue with my key not here:
http://www.apache.org/dist/logging/KEYS

The file has much more names than in the link above, but not all
necessary. I believe we should use the option by id.apache.org for
log4j2. For now I will add my key to the old file too, so the issue
should be fixed

Cheers
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

Ivan Habunek | 8 Dec 2012 12:26
Picon
Gravatar

Log4php git repository is live

Hi all,

Thanks to Gavin from Infra, our git repository is live as of today.
This marks the end of svn for log4php code. The svn repo will remain
available in read-only mode.

Here's the links you might need:

The official repository (and web interface), writable for developers:
https://git-wip-us.apache.org/repos/asf/logging-log4php.git

Official read-only mirror:
git://git.apache.org/logging-log4php.git

Github read-only mirror:
https://github.com/apache/logging-log4php

Note that the old apache and github mirrors, which were named
"log4php.git" instead of the current name "logging-log4php.git" will
be removed at some point in time, so don't use those for anything.

The github mirror is updated once daily. I was told that it's not
possible to update on commit since it's a mirror of the git.apache.org
mirror, and not of the main repository. I will look into possible ways
of improving this.

None of the other Logging Services projects are affected by this
change, except in a way to encourage them to move to git at some point
in time. The transition was very painless.

Best regards,
Ivan


Gmane