Apache Wiki | 25 Apr 07:29 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=33&rev2=34

   1. Run {{{mvn -P apache-release release:prepare release:perform}}} 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:-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
+  1. Run {{{mvn site}}} in the tag directory. When that completes run {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
   1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}} and copy to your account at
{{{people.apache.org}}} with {{{scp log4j.zip
myUsername <at> people.apache.org:/home/myUsername}}}. Unzip the contents into your public html directory.
   1. Generate the release vote email:
      a. Create the email addressed to log4j-dev <at> logging.apache.org and private <at> logging.apache.org.
Sending the email to the PMC is not strictly necessary, but due to the small size of the logging PMC it is
expedient to do so in order to get the required votes.

Apache Wiki | 25 Apr 03:27 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=32&rev2=33

   1. Run {{{mvn -P apache-release release:prepare release:perform}}} 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-deploy
-DstagingSiteURL=file:///$HOME/log4j}}} where {{{$HOME}}} is your home directory.
+  1. Run {{{mvn site}}} in the tag directory. When that completes run {{{mvn
site:-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
   1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}} and copy to your account at
{{{people.apache.org}}} with {{{scp log4j.zip
myUsername <at> people.apache.org:/home/myUsername}}}. Unzip the contents into your public html directory.
   1. Generate the release vote email:
      a. Create the email addressed to log4j-dev <at> logging.apache.org and private <at> logging.apache.org.
Sending the email to the PMC is not strictly necessary, but due to the small size of the logging PMC it is
expedient to do so in order to get the required votes.

Uwe Bohnhoff | 23 Mar 18:00 2015
Picon

Problem

Hi,

we have added log4net to our tools.

Now, we tried again to another tool and get this message:

 

    Public Shared ReadOnly bblog As log4net.ILog = log4net.LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType)

 

„LogManager“ is in Namespace „log4net“ not unique.

 

What is our problem in this tool. All tools created in Visual Studio 2012 with vb.net.

 

Best regards,

 

 

Mit freundlichen Grüßen

 

Uwe Bohnhoff
Bohnhoff Soft- und Hardware Systeme GmbH

*******************************************************************************
Bohnhoff Soft- und Hardware Systeme GmbH                 

Wilhelmstr. 66                                  

13593 Berlin                                     

                                                  

Tel.:    +49 (0)30 / 35 39 36 -0                 

Fax:    +49 (0)30 / 35 39 36 18                          

http://www.bohnhoff-gmbh.de

eMail: ubohnhoff <at> bohnhoff-gmbh.de    

 

Geschäftssitz: Berlin

HRB 33525 - Amtsgericht Berlin-Charlottenburg

Geschäftsführung: Birgit Nötzel

USt.-ID-Nr.: DE136573674

 

             

 

Dominik Psenner | 19 Mar 20:51 2015
Picon

Apache Con

Dear Apache Logging enthusiast,

In just a few weeks, we'll be holding ApacheCon in Austin, Texas, and we'd love to have you in attendance. You can save $300 on admission by registering NOW, since the early bird price ends on the 21st.

Register at http://s.apache.org/acna2015-reg

ApacheCon this year celebrates the 20th birthday of the Apache HTTP Server, and we'll have Brian Behlendorf, who started this whole thing, keynoting for us, and you'll have a chance to meet some of the original Apache Group, who will be there to celebrate with us.

We've got 7 tracks of great talks, as well as BOFs, the Apache BarCamp, project-specific hack events, and evening events where you can deepen your connection with the larger Apache community. See the full schedule at http://apacheconna2015.sched.org/

And if you have any questions, comments, or just want to hang out with us before and during the event, follow us on Twitter - <at> apachecon - or drop by #apachecon on the Freenode IRC network.

Hope to see you in Austin!

Ralph Goers | 27 Feb 05:49 2015

[ANNOUNCEMENT] Apache Log4j 2.2 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.2 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 fifth GA release. It contains several bugfixes and new features.

GA Release 2.2

Changes in this version include:

New features:
o LOG4J2-941: Allow JSON layout to create one compact log record per line. Thanks to Konstantinos Liakos.
o LOG4J2-933: HTML layout should not use attribute minimalization for hr noshade. Thanks to ppiman at gmail.com.
o LOG4J2-895: Specify the SyslogAppender connect timeout value as part of the configuration.
The SyslogAppender takes a new parameter connectTimeoutMillis.
o LOG4J2-899: Specify the SocketAppender connect timeout value as part of the configuration.
The SyslogAppender takes a new parameter connectTimeoutMillis.

Fixed Bugs:
o LOG4J2-938: (JMX) To avoid memory leaks when web applications are restarted, JMX notifications are sent from
the caller thread in web applications. For non-web applications notifications are sent from a background thread
as before. Thanks to Mauro Molinari.
o LOG4J2-957: Missing toUpperCase("Locale.ENGLISH"). Thanks to fatih guleryuz.
o LOG4J2-956: Manual refers to Route "AppenderRef" attribute, should be "ref". Thanks to David Kellerman.
o LOG4J2-944: Log4j Flume appender is not adding millisecond to the event headers when the event is logged at 000 milliseconds. Thanks to Vinayaka Ramachandra.
o LOG4J2-924: Log4j 1.2 Bridge doesn't map level ALL correctly in Category.getEffectiveLevel(). Thanks to Ryan Rupp.
o LOG4J2-931: ConsoleAppender is missing <at> PluginFactory annotation at createAppender method. Thanks to Robert Gacki.
o LOG4J2-919: Logging system fails to initialize if XInclude API is not available. Thanks to David Johle.
o LOG4J2-914: ThrowableProxy.getExtendedStackTraceAsString causes NullpointerException. Thanks to Kaj Bjurman.
o LOG4J2-912: XML configuration does not report full error message for XInclude parser configuration problems.
o LOG4J2-903: ClassLoaderContextSelector uses ClassLoader.toString() as a key Thanks to Mauro Molinari.
o LOG4J2-834: ThrowableProxy throws NoClassDefFoundError. Thanks to Nikita Koval, Leonard Broman, Thiago Kronig.
o LOG4J2-893: NullPointerException on filter when mapping JUL to Log4j2.
o LOG4J2-892: JUL adapter does not map Log4j'2 FATAL level to a JUL level.
o LOG4J2-881: AbstractLifecycle should not implement equals() and hashCode(). Thanks to Mariano Gonzalez.
o LOG4J2-897: Javadoc for org.apache.log4j.BasicConfigurator.configure() is incorrect.
o LOG4J2-891: AbstractLifecycle should not implement equals() and hashCode().
o LOG4J2-946: [docs] Using Log4j 2 in Web Applications: Update example (Log4jWebLifeCycle is not visible). Thanks to artemonster.

Changes:
o LOG4J2-955: Documentation: clarify system properties to control status logger, improve troubleshooting FAQ entry.
o LOG4J2-950: Incorrect attribute name in PropertiesRewritePolicy example. Thanks to Joel Edwards.
o LOG4J2-901: Update docs for SyslogAppender: "No structured id name was supplied" Thanks to Tihomir Meščić, Siegfried Greisinger.
o LOG4J2-958: Update from Jackson 2.5.0 to 2.5.1.
o LOG4J2-925: Update from Jackson 2.4.4 to 2.5.0.
o LOG4J2-910: Update Jackson from 2.4.3 to 2.4.4.
o LOG4J2-881: Update Jackson from 2.4.2 to 2.4.3.
o LOG4J2-882: Update maven-core from 3.1.0 to 3.2.3.
o LOG4J2-883: Update tests from org.apache.felix.framework 4.2.1 to 4.4.1.
o LOG4J2-884: Update org.eclipse.osgi from 3.6.0 to 3.7.1.
o LOG4J2-900: Update Apache Flume from 1.5.0.1 to 1.5.2.


Apache Log4j 2.2 requires a minimum of Java 6 to build and run. Future releases may require a minimum
of Java 7.

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/
Apache Wiki | 22 Feb 23:36 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=31&rev2=32

   1. Update {{{src/changes/announcement.vm}}}
   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 {{{svn commit}}} to commit the {{{RELEASE-NOTES.txt}}} file that was just generated.
+  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}}} 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.
+  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-deploy
-DstagingSiteURL=file:///$HOME/log4j}}} where {{{$HOME}}} is your home directory.
   1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}} and copy to your account at
{{{people.apache.org}}} with {{{scp log4j.zip
myUsername <at> people.apache.org:/home/myUsername}}}. Unzip the contents into your public html directory.
   1. Generate the release vote email:

Apache Wiki | 7 Nov 06:19 2014
Picon

[Logging Wiki] Update of "Log4j2AndHibernate4" by StefanBodewig

Dear Wiki user,

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

The "Log4j2AndHibernate4" page has been changed by StefanBodewig:
https://wiki.apache.org/logging/Log4j2AndHibernate4?action=diff&rev1=2&rev2=3

Comment:
new Hibernate release, still the same hassle

- As of this writing Hibernate 4.3.6.Final is the current version of Hibernate and it uses jboss-logging
Version 3.1.3.GA for logging.  jboss-logging 3.2.0.Beta2 will support log4j 2.x natively and no
additional configuration will be required, but it hasn't been released, yet.  Once it has been released,
most information on this page will become obsolete.
+ As of this writing Hibernate 4.3.7.Final is the current version of Hibernate and it uses jboss-logging
Version 3.1.3.GA for logging.  jboss-logging 3.2.0.Beta2 will support log4j 2.x natively and no
additional configuration will be required, but it hasn't been released, yet.  Once it has been released,
most information on this page will become obsolete.

  As a sidenote: jboss-logging 3.2.0.Beta1 claims to support log4j 2.x natively but was based on beta
releases of log4j 2.x - due to a [[https://issues.jboss.org/browse/JBLOGGING-107|backwards
incompatible change in log4j 2.x after its beta]] jboss-logging 3.2.0.Beta1 doesn't work with the final
release of log4j 2.x.

Ralph Goers | 24 Oct 17:27 2014

[ANNOUNCEMENT] Apache Log4j 2.1 released

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

This is the fourth GA release which contains several bugfixes and new features. There are two
new Maven artifacts in this release: log4j-jul and log4j-iostreams. Both components are API-based
with optional Core features.

GA Release 2.1

Changes in this version include:

New features:
o LOG4J2-868:  Add ShutdownCallbackRegistry interface for customizable shutdown callback handling.
This is particularly
        useful for application servers that wish to integrate with Log4j 2. 
o LOG4J2-589:  Supported filtering on custom log levels in configuration. 
o LOG4J2-856:  Documentation: add sections on the JUL Adapter, IO Streams and NoSQL Appenders to the Maven
and Ivy page. 
o LOG4J2-848:  Add a Java lookup to provide nicely formatted runtime version information. 
o LOG4J2-809:  Move reflection utility class to API's private utility classes. 
o LOG4J2-833:  Documentation: added Runtime Dependencies link to left nav-bar on site. 
o LOG4J2-816:  Documentation: added section on XInclude to user manual Configuration page. 
o LOG4J2-547:  Add the Log4j IOStreams component. 
o LOG4J2-431:  Added Memory-Mapped File Appender. Thanks to Claude Mamo. 
o LOG4J2-827:  Support use of TypeConverter classes through the standard Plugin system. 
o LOG4J2-825:  Add simple validation constraint annotations for the Plugin system. 
o LOG4J2-428:  Implement a GELF layout. Thanks to Mark Paluch. 
o LOG4J2-608:  Add java.util.logging implementation based on log4j-api. See log4j-jul documentation
for more details. 
o LOG4J2-793:  Add support for custom SLF4J Markers in log4j-slf4j-impl module. 
o LOG4J2-771:  Add lookup for application main arguments. 
o LOG4J2-787:  Add lookup for JVM arguments. 

Fixed Bugs:
o LOG4J2-676:  Some typo fixes and enhancements for the site. Thanks to Stefan Bodewig. 
o LOG4J2-866:  Documentation: fixed missing closing parenthesis in code example. Thanks to Gerard
Weatherby. 
o LOG4J2-862:  Fixed classloader issue that prevented Log4j from finding the implementation when used in a
custom Ant task. Thanks to Michael Sutherland. 
o LOG4J2-861:  Documentation: fix broken links on left navigation Extending Log4j Configuration
sub-menu. 
o LOG4J2-797:  Documentation: clarified why log4j-core is a compile time dependency in Maven and Ivy page.
Thanks to Andreas Rytina. 
o LOG4J2-855:  Documentation: fix broken links on Appenders manual page. 
o LOG4J2-807:  Prevent NPE when configuration with AsyncLogger/AsyncRoot is reloaded. 
o LOG4J2-678:  Documentation: fixed minor issues with Log4j2 web site/documentation. Thanks to Matt
Sicker. 
o LOG4J2-843:  Migrate JpaHyperSqlAppenderTest JUnit performance test to log4j-perf. 
o LOG4J2-842:  Migrate JpaH2AppenderTest JUnit performance test to log4j-perf. 
o LOG4J2-841:  Migrate JdbcHyperSqlAppenderTest JUnit performance test to log4j-perf. 
o LOG4J2-840:  Migrate JdbcH2AppenderTest JUnit performance test to log4j-perf. 
o LOG4J2-830:  Respect external interrupt signal to allow application shutdown after joining
AsyncAppender thread. 
o LOG4J2-813:  MarkerManager Log4jMarker.hasParents() returns opposite of correct result. Thanks to
David Erichsen, Brandon Barry. 
o LOG4J2-785:  Documentation: fixed capitalization inconsistency in user manual example config. 
o LOG4J2-829:  Fixed issue in RollingFile filePattern: backslashes are path separators, not escape
characters. 
o LOG4J2-832:  ThrowableProxy fails if a class in logged stack trace throws java.lang.Error from
initializer Thanks to Seth Leger. 
o LOG4J2-745:  Avoid ConverterKey plugin clashes by using a more predictable plugin loading infrastructure.
        Plugins have been segmented into three parts: class path, user-specified packages, and OSGi bundles.
Thanks to Scott Harrington. 
o LOG4J2-798:  Fixed plugin scanning redundancy causing massive slowdowns in certain environments.
Thanks to Scott Harrington. 
o LOG4J2-753:  Reduced CachedClock thread contention. 
o LOG4J2-819:  Fixed memory leak in Tomcat 6 caused by clock background threads unintentionally
        started by Tomcat after web application stop. Thanks to Gary Gregory. 
o LOG4J2-391:  FlumePersistentManager now handles LockConflictExceptions in Berkeley Db when sending a
batch. Thanks to Kamal Bahadur. 
o LOG4J2-782:  Remove invalid Oracle Maven repository. 
o LOG4J2-796:  Fixed issue where log4j-to-slf4j did not work correctly with SLF4J Simple Logger. 
o LOG4J2-811:  SimpleLogger throws ArrayIndexOutOfBoundsException for an empty array. Thanks to Yogesh
Rao. 
o LOG4J2-663:  Fix OSGi Import-Package problem with the JMS API. Thanks to Florian Brunner. 
o LOG4J2-783:  PatternLayout should use platform character encoding by default, not UTF-8. Thanks to
Minglei Lee. 

Changes:
o LOG4J2-845:  Add 2.1.0 to compatible versions in Log4j API ProviderUtil and update Log4jAPIVersion to
2.1.0 in
        core META-INF/log4j-provider.properties. 
o LOG4J2-844:  Update JMH to 1.1 from 0.7.2. 
o LOG4J2-831:  Documentation: updated FAQ "which jars" diagrams for JUL bridge and 2.1 version. 
o LOG4J2-780:  Update Spring Framework to 3.2.11.RELEASE from 3.2.8.RELEASE. 
o LOG4J2-815:  Unify the two JMS appenders into a single appender. Configurations written for 2.0 will
still work in 2.1+. 
o LOG4J2-790:  Update Jackson to 2.4.2 from 2.4.1 (for XML and JSON processing). 
o LOG4J2-766:  Incomplete documentation for JSONLayout. Thanks to Bruno P. Kinoshita. 
o LOG4J2-800:  All life cycle implementations should be serializable.
        This is still work in progress. 
o LOG4J2-801:  org.apache.logging.log4j.core.Logger should be serializable.
        This is still work in progress. 
o LOG4J2-810:  Update javax.mail to 1.5.2 from 1.5.0. 
o LOG4J2-822:  Update org.eclipse.persistence.jpa to 2.5.2 from 2.5.1. 
o LOG4J2-867:  FlumeAppender: maxDelay not in seconds, but milliseconds.
        Add time scale to some settings, for example maxDelayMillis instead of maxDelay.
        The old names are aliased for compatibility. 

Apache Log4j 2.1 requires a minimum of Java 6 to build and run. 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/

Apache Wiki | 20 Oct 06:17 2014
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=30&rev2=31

  If the release fails after sending the vote email:
   1. Login to http://repository.apache.org using your ASF credentials. Select "Staging Repositories"
then check the org.apache.logging repository and drop it.
   1. Rename the release tag in Git to add {{{rcn}}} to the end of the tag. '''Note that this may not be possible in
Git depending on configuration'''
+ {{{
+ git tag log4j-n.n log4j-n.n-rcn
+ git tag -d log4j-n.n
+ git push origin :refs/tags/log4j-n.n
+ git push --tags
+ }}}
-  1. Reset the version numbers in all of the poms back to the release snapshot.
+  1.#3 Reset the version numbers in all of the poms back to the release snapshot.
   1. Restart the release process as a new release candidate.

Apache Wiki | 13 Oct 17:53 2014
Picon

[Logging Wiki] Update of "Log4j2AndHibernate4" by StefanBodewig

Dear Wiki user,

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

The "Log4j2AndHibernate4" page has been changed by StefanBodewig:
https://wiki.apache.org/logging/Log4j2AndHibernate4?action=diff&rev1=1&rev2=2

Comment:
typo spetted by Dominik Psenner

   * add the log4j 2.x slf4j binding and slf4j-api to your classpath as well and set the system property
`org.jboss.logging.provider` to `slf4j` - setting the property explicitly bypasses the "logback is
there" check
   * override Hibernate's dependency to use jboss-logging 3.2.0.Beta1, add the log4j 1.x logging bridge to
your classpath as well and set the system property `org.jboss.logging.provider` to `log4j` - this
doesn't seem to work with any 3.1.x version of jboss-logging

- Things get even more complex if you add a non-default connection pool to Hibernate.  c3p0 prior to
0.9.5pre2 will only log to log4j 1.x so using the log4j 1.x logging bridge is your only option.  Later
versions of c3po added support for slf4j as well.
+ Things get even more complex if you add a non-default connection pool to Hibernate.  c3p0 prior to
0.9.5pre2 will only log to log4j 1.x so using the log4j 1.x logging bridge is your only option.  Later
versions of c3p0 added support for slf4j as well.

Apache Wiki | 13 Oct 14:15 2014
Picon

[Logging Wiki] Update of "Log4j2AndHibernate4" by StefanBodewig

Dear Wiki user,

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

The "Log4j2AndHibernate4" page has been changed by StefanBodewig:
https://wiki.apache.org/logging/Log4j2AndHibernate4

New page:
As of this writing Hibernate 4.3.6.Final is the current version of Hibernate and it uses jboss-logging
Version 3.1.3.GA for logging.  jboss-logging 3.2.0.Beta2 will support log4j 2.x natively and no
additional configuration will be required, but it hasn't been released, yet.  Once it has been released,
most information on this page will become obsolete.

As a sidenote: jboss-logging 3.2.0.Beta1 claims to support log4j 2.x natively but was based on beta
releases of log4j 2.x - due to a [[https://issues.jboss.org/browse/JBLOGGING-107|backwards
incompatible change in log4j 2.x after its beta]] jboss-logging 3.2.0.Beta1 doesn't work with the final
release of log4j 2.x.

jboss-logging is yet another layer on top of popular logging frameworks.  You can configure which logging
framework it should delegate to using the system property `org.jboss.logging.provider`, if it is not
set its discovery algorithm will try
 * jBoss' own logging implementation
 * log4j 2.x - starting with 3.2.0.Beta2
 * log4j 1.x - only if some internal log4j classes can be found
 * slf4j - only if logback is on the classpath as well
 * java.util.logging

in that order.  The possible values for the system property are `jboss`, `log4j2`, `log4j`, `slf4j` and `jdk`.

In order to use log4j2 with jboss-logging prior to 3.2.0.Beta2 you have two choices

 * add the log4j 2.x slf4j binding and slf4j-api to your classpath as well and set the system property
`org.jboss.logging.provider` to `slf4j` - setting the property explicitly bypasses the "logback is
there" check
 * override Hibernate's dependency to use jboss-logging 3.2.0.Beta1, add the log4j 1.x logging bridge to
your classpath as well and set the system property `org.jboss.logging.provider` to `log4j` - this
doesn't seem to work with any 3.1.x version of jboss-logging

Things get even more complex if you add a non-default connection pool to Hibernate.  c3p0 prior to 0.9.5pre2
will only log to log4j 1.x so using the log4j 1.x logging bridge is your only option.  Later versions of c3po
added support for slf4j as well.


Gmane