Entries tagged [release]

Thursday April 25, 2013

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.

New features:

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

Fixed Bugs:

  • LOG4J2-205: Fix deadlock in SocketAppender. Added option to not wait for socket reconnect.
  • LOG4J2-211: Removing extra spaces in entry and exit method output. Thanks to Nick Williams.
  • LOG4J2-212: Loggers without a "." had no parent logger.
  • LOG4J2-212: Call LoggerContext.stop when the application is shutdown.
  • LOG4J2-210: MapMessage was not enclosing key value in quotes when generating XML. Thanks to Arkin Yetis.
  • LOG4J2-198: FlumeAvroManager now uses Flume RPCClient.
  • LOG4J2-196: FlumeAvroManager now uses Flume RPCClient.
  • LOG4J2-207: Use the Maven group ID org.apache.logging.log4j for all artifacts.
  • LOG4J2-195: Unit tests now create files in the target directory. Thanks to Remko Popma.
  • LOG4J2-193: RollingFastFileAppender (in log4j-async) did not roll over. Thanks to Remko Popma.
  • LOG4J2-199: Highlight subprojects in sub-navigation. Thanks to Remko Popma.
  • LOG4J2-200: LoggerContext method renamed to removeFilter from removeFiler. Thanks to Remko Popma.
  • LOG4J2-194: ThrowableFormatOptionsTest failed on Windows due to CR/LF issue. Thanks to Remko Popma.
  • LOG4J2-190: BaseConfiguration addLoggerAppender saved appender using the Logger name. Thanks to Werner.
  • LOG4J2-189: The blocking parameter did not work properly on AsynchAppender. Thanks to Werner.
  • LOG4J2-188: appender-refs on AsynchAppender didn't support the level and filter elements. Thanks to Werner.
  • LOG4J2-176: Avoid IllegalArgumentException in AsynchAppender. Thanks to Remko Popma.
  • LOG4J2-181: OutputStreamManager now adds the layout header whenever the OutputStream is set.
  • LOG4J2-177: Fix NullPointerException in DatagramOutputStream when flush is called from multiple threads. Thanks to Remko Popma.
  • LOG4J2-175: Plugin cache should be reset when addPackages is called.
  • LOG4J2-159: Add Fragment-Host to MANIFEST.MF for log4j2-core. Thanks to Jan Winter.
  • LOG4J2-167: Configurator throws a ClassCastException if LogManager returns a SimpleLoggerContext.
  • LOG4J2-169: ConfigurationFactory was adding factories on every call.
  • LOG4J2-161: Modify ClassLoaderContextSelector to use the first ClassLoader in the child parent hierarchy that has a Context with a configuration to allow JSPs to use the WebApp's context and configuration.

Changes:

  • LOG4J2-214: Async documentation update. Thanks to Remko Popma.
  • LOG4J2-208: Move async subproject into core. Thanks to Remko Popma.
  • LOG4J2-160: Move Throwable pattern converter options processing to ThrowableFormatOptions class. Thanks to Joanne Polsky.
  • LOG4J2-157: Allowed Loggers access to the properties in the LoggerConfig. Thanks to Remko Popma.
  • LOG4J2-153: Added ability to include or exclude location information. Thanks to Remko Popma.
  • LOG4J2-151: Allow Logger and LoggerContext to be subclassed. Thanks to Remko Popma.

Apache Log4j 2.0-beta5 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/

Monday February 04, 2013

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

New features:

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

Fixed Bugs:

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

  • 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.
  • LOG4J2-128: Add follow attribute to Console Appender.
  • LOG4J2-122: Add unit test to verify exceptions are thrown when the socket connection fails.
  • 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:

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

Monday September 24, 2012

Apache log4j 2.0-beta1 released

The Apache Logging team is pleased to announce the Apache log4j 2.0-beta1 release! This is the third release of Log4j 2 and is being made available to encourage use and feedback from the community.

[Read More]

Sunday August 05, 2012

Apache Logging log4j 2.0-alpha1 released

The Apache Logging team is pleased to announce the Apache log4j 2.0-alpha1 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 first release of Log4j 2 and is being made available to get feedback from the community.

Some of the features and improvements in Log4j 2 are:


  • API Separation - The API for Log4j is separate from the implementation. It is now clear to application developers what classes and methods they can use with compatibility being assured, while also allowing improvements to be made to the implementation.

  • Designed for Audit Logging - Unlike Log4j 1.x and Logback, Log4j 2 will not lose events during reconfiguration. Log4j 2 also supports Messages, which easily allow audit events to be flow through the framework.

  • Improved Performance - Faster performance than Log4j 1.x in critical areas and similar performance to Logback in most circumstances.

  • Support for multiple APIs - While the Log4j 2 API will provide the best performance, support for SLF4J and Commons Logging APIs are provided.

  • Automatic Reloading of Configurations - Like Logback, Log4j 2 supports filtering based on context data, markers, regular expressions and other components in the Log event and can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. In addition, filters can also be associated with Loggers, Unlike Logback, a common Filter class can be used in any of these circumstances. Log4j 2 currently supports configuration via XML or JSON.

  • Plugin Architecture - All configurable components are defined as Log4j plugins. As such, no Log4j code must be changed to create a new Appender, Layout, Pattern Converter, etc. Log4j will automatically recognize properly defined plugins and use them when they are referenced in the configuration.

  • Property Support - Properties can be referenced in the configuration and either be directly replace or passed to the underlying component where they can be dynamically resolved. Properties can come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event. Users can further customize the property providers by adding their own Lookup Plugin

For more information see the Log4j 2 web site

Apache log4j 2.0 requires JDK 5 or later.

Monday May 28, 2012

Apache Logging log4j 1.2.17 released

The Apache Logging team is pleased to announce the Apache log4j 1.2.17 release!

[Read More]

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation