logging-log4j2 icon indicating copy to clipboard operation
logging-log4j2 copied to clipboard

Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.

Results 483 logging-log4j2 issues
Sort by recently updated
recently updated
newest added

### Problem Description Our web application, which runs in Tomcat 11 and Java 21, uses **SLF4J + Logback** for logging. However, it allows dynamically importing extensions along with JARs at...

waiting-for-maintainer

It is too easy to write code like this: ``` try { doThing(); } catch (ThingFailedException ex) { logger.error("Doing this thing failed."); logger.error("Context ID: " + context.id); logger.error("SomeSettings: " +...

waiting-for-maintainer

## Description When using `DefaultLogBuilder` log* methods, `throwable` information that might have been inferred by the created `Message` object is lost - and `DefaultLogBuilder` only passes the explicit `throwable` that...

bug
api
waiting-for-maintainer

This PR updates InternalLoggerRegistry to automatically remove stale loggers when its methods are invoked. Changes Introduced: Introduced a ReferenceQueue to track loggers that have been reclaimed by the garbage collector....

This is a parallel of Ticket #3153 for the main (3.x) branch. StringMatchFilter: + add validation on 'text' attribute to class constructor and builder (non-blank) + add JVerify nullability annotations...

bug
java
configuration

Currently `log4j-plugin-processor` in version `3.0.0-beta3` of Log4j Core adds [BND annotations](https://bnd.bndtools.org/chapters/230-manifest-annotations.html) to the generated code. While these might be useful for OSGi users, they cause a compilation error if the...

waiting-for-maintainer

Log4j 2.24.3 .---- The `DefaultPropertyComponentBuilder `does not generate a valid Property Component. A Log4j XML configuration property should look like this: `` However, if the `ConfigurationBuilder.newProperty("p1", "foobar")` is called, it...

Log4j 2.24.3 -------- A `KeyValuePair` without a key is useless (since it cannot be referenced). A `null` key will also cause problems in multiple locations when added to Map implementations....

This issue is to remember to remove the Error Prone workaround from `log4j-parent/pom.xml`, once the fix is integrated into `logging-parent`.

Attempt to fix the flaky `RollingRandomAppenderDirectWriteAndSwitchDirectoryTest`.