Search by property

Jump to: navigation, search

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Full description" with value "Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x: API Separation: The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. Improved Performance: Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios Asynchronous Loggers have 10 times higher throughput and orders of magnitude lower latency than Log4j 1.x. Support for multiple APIs: While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and Commons Logging APIs. Automatic Reloading of Configurations: Log4j 2 can automatically reload its configuration upon modification. It will do so without losing log events while reconfiguration is taking place. Advanced Filtering: Log4j 2 supports filtering based on context data, markers, regular expressions, and other components in the Log event. Filtering can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. Plugin Architecture: Log4j uses the plugin pattern to configure components. As such, no code is needed to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically recognizes plugins and uses them when a configuration references them. Property Support: Properties can be referenced in a configuration, Log4j will directly replace them, or Log4j will pass them to an underlying component that will dynamically resolve them. Properties come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event.". Since there have been only a few results, also nearby values are displayed.

Showing below up to 2 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


    

List of results

    • Apache Log4j 2  + (Apache Log4j 2 is an upgrade to Log4j thatApache Log4j 2 is an upgrade to Log4j that provides significant</br>improvements over its predecessor, Log4j 1.x:</br></br>API Separation: The API for Log4j is separate from the</br>implementation making it clear for application developers which</br>classes and methods they can use while ensuring forward</br>compatibility.</br></br>Improved Performance: Log4j 2 contains next-generation</br>Asynchronous Loggers based on the LMAX Disruptor library. In</br>multi-threaded scenarios Asynchronous Loggers have 10 times</br>higher throughput and orders of magnitude lower latency than</br>Log4j 1.x.</br></br>Support for multiple APIs: While the Log4j 2 API will provide the</br>best performance, Log4j 2 provides support for the SLF4J and</br>Commons Logging APIs.</br></br>Automatic Reloading of Configurations: Log4j 2 can automatically</br>reload its configuration upon modification. It will do so without</br>losing log events while reconfiguration is taking place.</br></br>Advanced Filtering: Log4j 2 supports filtering based on context</br>data, markers, regular expressions, and other components in the</br>Log event. Filtering can be specified to apply to all events</br>before being passed to Loggers or as they pass through Appenders.</br></br>Plugin Architecture: Log4j uses the plugin pattern to configure</br>components. As such, no code is needed to create and configure an</br>Appender, Layout, Pattern Converter, and so on. Log4j</br>automatically recognizes plugins and uses them when a</br>configuration references them.</br></br>Property Support: Properties can be referenced in a</br>configuration, Log4j will directly replace them, or Log4j will</br>pass them to an underlying component that will dynamically</br>resolve them. Properties come from values defined in the</br>configuration file, system properties, environment variables, the</br>ThreadContext Map, and data present in the event.ontext Map, and data present in the event.)


    Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.

    The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.