[PR] Remove APR pool from Logger constructor in next ABI version [logging-log4cxx]

swebb2066 opened a new pull request, #392: URL: https://github.com/apache/logging-log4cxx/pull/392 No memory pool should live as long as a Log4cxx logger. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above t

Re: [PR] Fix building with mingw-w64-gcc [logging-log4cxx]

swebb2066 commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2226577724 > The following tests FAILED: > 52 - telnetappendertestcase (Timeout) When telnet appender is not explictly closed, the onexit processing chain does not terminat

Re: [PR] Fix building with mingw-w64-gcc [logging-log4cxx]

swebb2066 commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2226553813 Before using gdb, you need to ensure the directory contain log4cxx.dll is named on the path. For example, � export PATH=/home/steph/logging-log4cxx/buildsrc/main/cpp

Re: [I] CustomAppender Example - Class Not Found [logging-log4cxx]

rm5248 commented on issue #391: URL: https://github.com/apache/logging-log4cxx/issues/391#issuecomment-2226393670 Probably the issue is that your naming is incorrect. The macro `DECLARE_LOG4CXX_OBJECT(NullWriterAppender)` maps to the name of the class, and it is this name(`NullWriter

[I] CustomAppender Example - Class Not Found [logging-log4cxx]

sylphrena0 opened a new issue, #391: URL: https://github.com/apache/logging-log4cxx/issues/391 I'm attempting to create a custom layout to support RFC5424 (see #390), however, I receive a class not found error after compiling my layout and attempting to load the configuration. I attempted t

Re: [I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

vy commented on issue #2737: URL: https://github.com/apache/logging-log4j2/issues/2737#issuecomment-2225755922 @aaaygupta, Log4j version `2.23.1` changed the way `StatusLogger` is initialized. This works fine with modern JVMs, but, [as I indicated earlier and asked you to upgrade your J9

Re: [I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

aaaygupta commented on issue #2737: URL: https://github.com/apache/logging-log4j2/issues/2737#issuecomment-2225692494 > @aaaygupta, could you try placing `static { org.apache.logging.log4j.status.StatusLogger.getLogger().error("test"); }` just above the `... Logger = LogManager...` line in

Re: [I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

vy commented on issue #2737: URL: https://github.com/apache/logging-log4j2/issues/2737#issuecomment-2225617230 @aaaygupta, could you try placing `static { org.apache.logging.log4j.status.StatusLogger.getLogger().error("test"); }` just above the `... Logger = LogManager...` line in `TestLog

Re: [I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

aaaygupta commented on issue #2737: URL: https://github.com/apache/logging-log4j2/issues/2737#issuecomment-2225594374 @vy Sorry, for the wrong error stack before I have updated the stack in the description. Please have a look now -- This is an automated message from the Apache Git Servic

Re: [PR] Fix building with mingw-w64-gcc [logging-log4cxx]

MehdiChinoune commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2225583980 @swebb2066 What did you to debug. I built it with `CMAKE_BUILD_TYPE=Debug` with no luck! -- This is an automated message from the Apache Git Service. To respond to the mes

Re: [PR] Revamp the `Lookups` page (logging-log4j2)

vy commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1675594018 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configuration

Re: [PR] Bump github/codeql-action from 3.25.11 to 3.25.12 [logging-parent]

github-actions[bot] closed pull request #204: Bump github/codeql-action from 3.25.11 to 3.25.12 URL: https://github.com/apache/logging-parent/pull/204 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [PR] Bump flapdoodle-embed.version from 4.12.0 to 4.13.0 (logging-log4j2)

github-actions[bot] closed pull request #2739: Bump flapdoodle-embed.version from 4.12.0 to 4.13.0 URL: https://github.com/apache/logging-log4j2/pull/2739 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to g

Re: [PR] Bump flapdoodle-embed.version from 4.11.0 to 4.13.0 (logging-log4j2)

github-actions[bot] closed pull request #2738: Bump flapdoodle-embed.version from 4.11.0 to 4.13.0 URL: https://github.com/apache/logging-log4j2/pull/2738 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to g

Re: [I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

vy commented on issue #2737: URL: https://github.com/apache/logging-log4j2/issues/2737#issuecomment-2225127699 @aaaygupta, the stack trace doesn't really make sense to me. I cannot think of a way `Config.getInstance().fallbackListenerLevel` (`StatusLogger.java:533`) returns null. I am susp

[I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

aaaygupta opened a new issue, #2737: URL: https://github.com/apache/logging-log4j2/issues/2737 ## Description I have created a java sample where I am only initializing the logger using LogManager. Below is my sample code ``` import org.apache.logging.log4j.LogManager;