Re: [I] Fails to build with mingw-w64-gcc [logging-log4cxx]

2024-07-09 Thread via GitHub
MehdiChinoune commented on issue #388: URL: https://github.com/apache/logging-log4cxx/issues/388#issuecomment-2216922014 You don't understand In MSYS2 we have many environments/variants https://www.msys2.org/docs/environments/ In MINGW64 libstdc++ is the default c++ library and It's u

Re: [I] `PatternResolver` does not support substitution (logging-log4j2)

2024-07-09 Thread via GitHub
ppkarwasz commented on issue #2666: URL: https://github.com/apache/logging-log4j2/issues/2666#issuecomment-2217034113 **Remark**: You can easily workaround the problem with the evaluation of `${env:TZ:-%d{-MM-dd HH:mm:ss.SSS}{UTC+07}}` by: * either defining a `TZ` configuration p

Re: [PR] StrSubstitutor cannot parse nested braces (logging-log4j2)

2024-07-09 Thread via GitHub
ngocnhan-tran1996 closed pull request #2712: StrSubstitutor cannot parse nested braces URL: https://github.com/apache/logging-log4j2/pull/2712 -- 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 the spe

Re: [PR] StrSubstitutor cannot parse nested braces (logging-log4j2)

2024-07-09 Thread via GitHub
ngocnhan-tran1996 commented on PR #2712: URL: https://github.com/apache/logging-log4j2/pull/2712#issuecomment-2217232851 @ppkarwasz I see, thanks for your help. I will close this PR -- This is an automated message from the Apache Git Service. To respond to the message, please log o

Re: [I] `StrSubstitutor` cannot parse nested braces (logging-log4j2)

2024-07-09 Thread via GitHub
ppkarwasz commented on issue #2679: URL: https://github.com/apache/logging-log4j2/issues/2679#issuecomment-2217263541 After discussing in with @vy on Slack, I believe we should coherently use `$` as escape character, with the following rules: 1. The escape character `$` only applies

Re: [I] Fails to build with mingw-w64-gcc [logging-log4cxx]

2024-07-09 Thread via GitHub
swebb2066 commented on issue #388: URL: https://github.com/apache/logging-log4cxx/issues/388#issuecomment-2217522030 > In MSYS2 we have many environments/variants So what macros are provided to determine the default threading backend? -- This is an automated message from the Apache

Re: [I] `StrSubstitutor` cannot parse nested braces (logging-log4j2)

2024-07-09 Thread via GitHub
ngocnhan-tran1996 commented on issue #2679: URL: https://github.com/apache/logging-log4j2/issues/2679#issuecomment-2217727929 I am looking forward to log4j2 new version, so many things have to done :D -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [I] Cache LoggerContext in log4j-slf4j-impl (logging-log4j2)

2024-07-09 Thread via GitHub
blaghed commented on issue #2720: URL: https://github.com/apache/logging-log4j2/issues/2720#issuecomment-2217835213 Thanks for having a look. After receiving your feedback and going again through the mentioned code, I can't really find a nice way to "cache" the `LoggerContext` in order t

Re: [I] Cache LoggerContext in log4j-slf4j-impl (logging-log4j2)

2024-07-09 Thread via GitHub
ppkarwasz commented on issue #2720: URL: https://github.com/apache/logging-log4j2/issues/2720#issuecomment-2217954069 @blaghed, > After receiving your feedback and going again through the mentioned code, I can't really find a nice way to "cache" the `LoggerContext` in order to preve

Re: [I] Fails to build with mingw-w64-gcc [logging-log4cxx]

2024-07-09 Thread via GitHub
MehdiChinoune commented on issue #388: URL: https://github.com/apache/logging-log4cxx/issues/388#issuecomment-2217982734 > > In MSYS2 we have many environments/variants > > So what macros are provided to determine the default threading backend? That's what I am asking the maint

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

2024-07-09 Thread via GitHub
MehdiChinoune opened a new pull request, #389: URL: https://github.com/apache/logging-log4cxx/pull/389 (no comment) -- 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 the specific comment. To unsub

Re: [I] Cache LoggerContext in log4j-slf4j-impl (logging-log4j2)

2024-07-09 Thread via GitHub
vy closed issue #2720: Cache LoggerContext in log4j-slf4j-impl URL: https://github.com/apache/logging-log4j2/issues/2720 -- 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 the specific comment. To unsu

Re: [I] SimpleLayout in log4j-1.2-api does not log anything (logging-log4j2)

2024-07-09 Thread via GitHub
vy closed issue #2722: SimpleLayout in log4j-1.2-api does not log anything URL: https://github.com/apache/logging-log4j2/issues/2722 -- 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 the specific comme

Re: [I] SimpleLayout in log4j-1.2-api does not log anything (logging-log4j2)

2024-07-09 Thread via GitHub
vy commented on issue #2722: URL: https://github.com/apache/logging-log4j2/issues/2722#issuecomment-2218431608 @kojinoguchi, `SimpleLayout` is by design a no-op. When a Log4j 1 configuration is read, `SimpleLayout` component will be replaced with a `PatternLayout` – see `SimpleLayoutBuilde

Re: [I] SimpleLayout in log4j-1.2-api does not log anything (logging-log4j2)

2024-07-09 Thread via GitHub
kojinoguchi commented on issue #2722: URL: https://github.com/apache/logging-log4j2/issues/2722#issuecomment-2218438839 > When a Log4j 1 configuration is read, SimpleLayout component will be replaced with a PatternLayout > Aaah, I see. In that case, I would have preferred if this em

Re: [PR] Consolidate stack trace rendering in Pattern Layout (logging-log4j2)

2024-07-09 Thread via GitHub
rgoers commented on PR #2691: URL: https://github.com/apache/logging-log4j2/pull/2691#issuecomment-2218458104 I do like Piotr's proposal of configuring the stack trace as a sub-element. However, I would do that as a separate follow-on item. The work being proposed here is already fairly inv

Re: [PR] Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 [logging-log4j-transform]

2024-07-09 Thread via GitHub
github-actions[bot] closed pull request #112: Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 URL: https://github.com/apache/logging-log4j-transform/pull/112 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abo

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

2024-07-09 Thread via GitHub
rm5248 commented on code in PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#discussion_r1671389085 ## CMakeLists.txt: ## @@ -170,35 +170,33 @@ IF(MSVC AND BUILD_SHARED_LIBS AND LOG4CXX_INSTALL_PDB) ) ENDIF() -if(UNIX) - # Support for pkg-config in consumi

Re: [PR] Bump org.assertj:assertj-bom from 3.26.0 to 3.26.3 [logging-log4j-samples]

2024-07-09 Thread via GitHub
github-actions[bot] closed pull request #155: Bump org.assertj:assertj-bom from 3.26.0 to 3.26.3 URL: https://github.com/apache/logging-log4j-samples/pull/155 -- 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

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

2024-07-09 Thread via GitHub
MehdiChinoune commented on code in PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#discussion_r1671562294 ## CMakeLists.txt: ## @@ -170,35 +170,33 @@ IF(MSVC AND BUILD_SHARED_LIBS AND LOG4CXX_INSTALL_PDB) ) ENDIF() -if(UNIX) - # Support for pkg-config in

Re: [I] Replace `synchronized` blocks with locks for performance in virtual threads (logging-log4j2)

2024-07-10 Thread via GitHub
vy commented on issue #1532: URL: https://github.com/apache/logging-log4j2/issues/1532#issuecomment-2219750778 I don't think this issue will be relevant anymore after Java 23, see [this heads-up notice from the OpenJDK team addressing pinning issues in `synchronized`](https://inside.java/2

[I] Official website down (logging-log4j2)

2024-07-10 Thread via GitHub
PerfectSlayer opened a new issue, #2727: URL: https://github.com/apache/logging-log4j2/issues/2727 Hello, Not sure where to report this but the related Apache website looks down: ![image](https://github.com/apache/logging-log4j2/assets/1766222/8b7f516f-535e-4195-a443-df72cf53bae6)

Re: [I] Official website down (logging-log4j2)

2024-07-10 Thread via GitHub
vy commented on issue #2727: URL: https://github.com/apache/logging-log4j2/issues/2727#issuecomment-2219989710 @PerfectSlayer, yes, thanks for the heads up. We are aware of the issue. It is an ASF-wide infrastructural problem, there are more project websites affected – INFRA is working on

Re: [I] Official website down (logging-log4j2)

2024-07-10 Thread via GitHub
PerfectSlayer commented on issue #2727: URL: https://github.com/apache/logging-log4j2/issues/2727#issuecomment-2220020580 Thanks for the staging link @vy ! Feel free to close the issue as it looks like things are being taken care of 👌 -- This is an automated message from the Apache Gi

Re: [PR] Bump org.apache:apache from 32 to 33 [logging-parent]

2024-07-10 Thread via GitHub
github-actions[bot] closed pull request #203: Bump org.apache:apache from 32 to 33 URL: https://github.com/apache/logging-parent/pull/203 -- 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 the specific

Re: [I] Official website down (logging-log4j2)

2024-07-10 Thread via GitHub
vy closed issue #2727: Official website down URL: https://github.com/apache/logging-log4j2/issues/2727 -- 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 the specific comment. To unsubscribe, e-mail: n

Re: [I] Official website down (logging-log4j2)

2024-07-10 Thread via GitHub
vy commented on issue #2727: URL: https://github.com/apache/logging-log4j2/issues/2727#issuecomment-2220157091 As of this moment, website is back! :tada: -- 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]

2024-07-10 Thread via GitHub
swebb2066 commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2220200496 Coul you please post versions of mingw environments and compilers you have tested this PR with? -- This is an automated message from the Apache Git Service. To respond to the me

Re: [PR] Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 (logging-log4j2)

2024-07-10 Thread via GitHub
github-actions[bot] closed pull request #2730: Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 URL: https://github.com/apache/logging-log4j2/pull/2730 -- 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] Fix building with mingw-w64-gcc [logging-log4cxx]

2024-07-10 Thread via GitHub
MehdiChinoune commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2220278237 > Coul you please post versions of mingw environments and compilers you have tested this PR with? UCRT64: GCC 14.1.0 + Binutils 2.42 CLANG64: Clang 18.1.8 CMak

Re: [PR] Bump net.bytebuddy:byte-buddy from 1.14.17 to 1.14.18 (logging-log4j2)

2024-07-10 Thread via GitHub
github-actions[bot] closed pull request #2723: Bump net.bytebuddy:byte-buddy from 1.14.17 to 1.14.18 URL: https://github.com/apache/logging-log4j2/pull/2723 -- 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

Re: [PR] Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 (logging-log4j2)

2024-07-10 Thread via GitHub
ppkarwasz commented on PR #2728: URL: https://github.com/apache/logging-log4j2/pull/2728#issuecomment-2221266642 @dependabot rebase -- 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 the specific co

Re: [PR] Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 (logging-log4j2)

2024-07-10 Thread via GitHub
github-actions[bot] closed pull request #2728: Bump org.assertj:assertj-core from 3.26.0 to 3.26.3 URL: https://github.com/apache/logging-log4j2/pull/2728 -- 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] Fix building with mingw-w64-gcc [logging-log4cxx]

2024-07-10 Thread via GitHub
swebb2066 commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2221742282 > Tests: 61/64 Could you post output of the tests that are failing? -- This is an automated message from the Apache Git Service. To respond to the message, please log on t

Re: [PR] Bump mongodb.version from 5.1.1 to 5.1.2 (logging-log4j2)

2024-07-10 Thread via GitHub
ppkarwasz commented on PR #2729: URL: https://github.com/apache/logging-log4j2/pull/2729#issuecomment-2221991311 @dependabot rebase -- 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 the specific co

Re: [PR] Bump mongodb.version from 5.1.1 to 5.1.2 (logging-log4j2)

2024-07-10 Thread via GitHub
github-actions[bot] closed pull request #2729: Bump mongodb.version from 5.1.1 to 5.1.2 URL: https://github.com/apache/logging-log4j2/pull/2729 -- 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 the sp

Re: [I] Replace `synchronized` blocks with locks for performance in virtual threads (logging-log4j2)

2024-07-11 Thread via GitHub
vy commented on issue #1532: URL: https://github.com/apache/logging-log4j2/issues/1532#issuecomment-302314 > It will still be somewhat relevant, because object monitors are expected to remain less performant on VT (see Ron's comment on https://mail.openjdk.org/pipermail/loom-dev/2024-J

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

2024-07-11 Thread via GitHub
ppkarwasz opened a new pull request, #2736: URL: https://github.com/apache/logging-log4j2/pull/2736 We revamp the `Lookups` page by: * Adding information on different evaluation contexts supported by lookups. * Adding a cheatsheet on which lookup is available in which evaluation co

Re: [I] Replace `synchronized` blocks with locks for performance in virtual threads (logging-log4j2)

2024-07-11 Thread via GitHub
zekronium commented on issue #1532: URL: https://github.com/apache/logging-log4j2/issues/1532#issuecomment-874228 @vy Thank you for opening the issue, maybe this would help it land sooner than version 3. The places where I encountered pinning are all fixed in 3 so I hope its easy to po

Re: [PR] Bump co.elastic.clients:elasticsearch-java from 8.14.2 to 8.14.3 (logging-log4j2)

2024-07-11 Thread via GitHub
github-actions[bot] closed pull request #2731: Bump co.elastic.clients:elasticsearch-java from 8.14.2 to 8.14.3 URL: https://github.com/apache/logging-log4j2/pull/2731 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the U

Re: [PR] Bump org.apache.maven.surefire:surefire-junit47 from 3.3.0 to 3.3.1 (logging-log4j2)

2024-07-11 Thread via GitHub
github-actions[bot] closed pull request #2732: Bump org.apache.maven.surefire:surefire-junit47 from 3.3.0 to 3.3.1 URL: https://github.com/apache/logging-log4j2/pull/2732 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use th

[I] RFC5424 Support [logging-log4cxx]

2024-07-11 Thread via GitHub
sylphrena0 opened a new issue, #390: URL: https://github.com/apache/logging-log4cxx/issues/390 It doesn't appear that there is an equivalent implementation of [Log4j2's RFC5424 Layout](https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout) to support the enhanced Syslog sp

Re: [PR] Bump org.springframework.cloud:spring-cloud-context from 4.1.3 to 4.1.4 (logging-log4j2)

2024-07-11 Thread via GitHub
github-actions[bot] closed pull request #2733: Bump org.springframework.cloud:spring-cloud-context from 4.1.3 to 4.1.4 URL: https://github.com/apache/logging-log4j2/pull/2733 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and us

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

2024-07-11 Thread via GitHub
MehdiChinoune commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2223870103 > Could you post output of the tests that are failing? ``` $ ctest --output-on-failure Test project D:/dev/build Start 1: autoconfiguretestcase 1/64 T

Re: [PR] Bump org.springframework:spring-framework-bom from 6.1.10 to 6.1.11 [logging-log4j-jakarta]

2024-07-11 Thread via GitHub
github-actions[bot] merged PR #38: URL: https://github.com/apache/logging-log4j-jakarta/pull/38 -- 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 the specific comment. To unsubscribe, e-mail: notifica

Re: [PR] Bump spring-framework.version from 6.1.10 to 6.1.11 (logging-log4j2)

2024-07-11 Thread via GitHub
github-actions[bot] closed pull request #2734: Bump spring-framework.version from 6.1.10 to 6.1.11 URL: https://github.com/apache/logging-log4j2/pull/2734 -- 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] RFC5424 Support [logging-log4cxx]

2024-07-11 Thread via GitHub
rm5248 commented on issue #390: URL: https://github.com/apache/logging-log4cxx/issues/390#issuecomment-2223978716 There are currently no plans to support the enhanced syslog format, as nobody has requested it. If anybody is interested in supporting this, it should be simple to modify

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

2024-07-11 Thread via GitHub
swebb2066 commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2224231025 > Line 439: Compare::compare(TEMP, LOG4CXX_FILE("witness/patternLayout.14")) was expected to be true, was false. > Files [output/patternlayout] and [witness/patternLayout.14] di

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

2024-07-11 Thread via GitHub
swebb2066 commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2224406427 > The following tests FAILED: > 2 - asyncappendertestcase (Exit code 0xc374 > With the following change to add some debug statements: ``` diff --git a/

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

2024-07-11 Thread via GitHub
MehdiChinoune commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2224418685 UCRT runtime comes from Windows OS, We could do nothing about. Could we keep this PR about "Fix building" instead of "Fix running"? -- This is an automated message from th

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

2024-07-11 Thread via GitHub
MehdiChinoune commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2224423229 Also MinGW apps are native Windows and shouldn't have any issue with `\` used in paths. -- This is an automated message from the Apache Git Service. To respond to the messag

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

2024-07-11 Thread via GitHub
swebb2066 commented on PR #389: URL: https://github.com/apache/logging-log4cxx/pull/389#issuecomment-2224622850 > Also MinGW apps are native Windows and shouldn't have any issue with \ used in paths. I believe locationinfo.h needs to set LOG4CXX_SHORT_FILENAME_SPLIT_CHAR based on the

Re: [PR] Bump org.apache.maven.surefire:surefire-junit47 from 3.3.0 to 3.3.1 (logging-log4j2)

2024-07-11 Thread via GitHub
github-actions[bot] closed pull request #2735: Bump org.apache.maven.surefire:surefire-junit47 from 3.3.0 to 3.3.1 URL: https://github.com/apache/logging-log4j2/pull/2735 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use th

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

2024-07-12 Thread via GitHub
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;

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

2024-07-12 Thread via GitHub
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

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

2024-07-12 Thread via GitHub
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: [PR] Bump flapdoodle-embed.version from 4.12.0 to 4.13.0 (logging-log4j2)

2024-07-12 Thread via GitHub
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 github/codeql-action from 3.25.11 to 3.25.12 [logging-parent]

2024-07-12 Thread via GitHub
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] Revamp the `Lookups` page (logging-log4j2)

2024-07-12 Thread via GitHub
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] Fix building with mingw-w64-gcc [logging-log4cxx]

2024-07-12 Thread via GitHub
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: [I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

2024-07-12 Thread via GitHub
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: [I] ExceptionInInitializerError caused by NullPointerException thrown by StatusConsoleListener log4j2 2.23.1 (logging-log4j2)

2024-07-12 Thread via GitHub
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)

2024-07-12 Thread via GitHub
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)

2024-07-12 Thread via GitHub
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

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

2024-07-12 Thread via GitHub
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] CustomAppender Example - Class Not Found [logging-log4cxx]

2024-07-12 Thread via GitHub
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

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

2024-07-12 Thread via GitHub
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: [PR] Fix building with mingw-w64-gcc [logging-log4cxx]

2024-07-12 Thread via GitHub
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

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

2024-07-12 Thread via GitHub
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] Remove APR pool from Logger constructor in next ABI version [logging-log4cxx]

2024-07-13 Thread via GitHub
rm5248 commented on PR #392: URL: https://github.com/apache/logging-log4cxx/pull/392#issuecomment-2226909411 Would it make sense to create a new branch(e.g. `log4cxx-next` or something like that) to do this type of refactoring in? It might make it a bit cleaner rather than having a bunch o

[I] log4net in MAUI application (logging-log4net)

2024-07-13 Thread via GitHub
TheSundayDev opened a new issue, #153: URL: https://github.com/apache/logging-log4net/issues/153 Hi all, I'm migrating from xamarin form to MAUI (ios and android) and one library has log4net as dependency. I have the exception below. How can I solve it? thanks a lot [DOTNE

Re: [I] log4net in MAUI application (logging-log4net)

2024-07-13 Thread via GitHub
FreeAndNil commented on issue #153: URL: https://github.com/apache/logging-log4net/issues/153#issuecomment-2227037784 @TheSundayDev do you have a config file? If yes, can you post the content? If not, can you create one? Do you have a reference on System.Configuration? -- This is

Re: [I] log4net in MAUI application (logging-log4net)

2024-07-13 Thread via GitHub
TheSundayDev commented on issue #153: URL: https://github.com/apache/logging-log4net/issues/153#issuecomment-2227122521 Thanks for your quick reply! Reference to System.Configuration.ConfigurationManager added. I created a app.config file in project root and mark as Embedded resource.

Re: [I] Logging overhead due to unnecessary pessimism [logging-log4cxx]

2024-07-13 Thread via GitHub
swebb2066 commented on issue #347: URL: https://github.com/apache/logging-log4cxx/issues/347#issuecomment-2227157338 After #351, the benchmark comparing the current implementation (lock and copy appender pointers) versas no coping or lock on gcc 11 indicates a 30-40 ns overhead from the co

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

2024-07-13 Thread via GitHub
swebb2066 commented on PR #392: URL: https://github.com/apache/logging-log4cxx/pull/392#issuecomment-2227160668 > Would it make sense to create a new branch On reflection, I am now inclined to add new methods in 1.3 and generate deprecated warnings on the functions to be removed i

Re: [I] log4net in MAUI application (logging-log4net)

2024-07-13 Thread via GitHub
FreeAndNil commented on issue #153: URL: https://github.com/apache/logging-log4net/issues/153#issuecomment-2227211386 @TheSundayDev embedded ressource is wrong. The config file must be copied as is to the target directory (the default build action for config files) Is the exception still

Re: [I] [MS17] Documentation revamp 4/5 (logging-log4j2)

2024-07-14 Thread via GitHub
grobmeier closed issue #2541: [MS17] Documentation revamp 4/5 URL: https://github.com/apache/logging-log4j2/issues/2541 -- 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 the specific comment. To unsub

Re: [I] [MS17] Documentation revamp 4/5 (logging-log4j2)

2024-07-14 Thread via GitHub
grobmeier commented on issue #2541: URL: https://github.com/apache/logging-log4j2/issues/2541#issuecomment-2227259561 Closing as completed -- 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 the spe

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677418429 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677494926 ## src/site/antora/modules/ROOT/examples/manual/lookups/MainArgsExample.java: ## @@ -0,0 +1,43 @@ +/* + * Licensed to the Apache Software Foundation (ASF) unde

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677544025 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677544411 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677544751 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677545049 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677548084 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677549963 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677554285 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677616123 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -16,63 +16,298 @@ = Lookups -Lookups provide a way to add values to the Log4j configu

Re: [PR] Bump org.apache.tomcat:tomcat-juli from 10.1.25 to 10.1.26 (logging-log4j2)

2024-07-15 Thread via GitHub
github-actions[bot] closed pull request #2740: Bump org.apache.tomcat:tomcat-juli from 10.1.25 to 10.1.26 URL: https://github.com/apache/logging-log4j2/pull/2740 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abo

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677884231 ## src/site/antora/modules/ROOT/pages/manual/lookups.adoc: ## @@ -89,561 +324,475 @@ It supports the retrieval of following container attributes: |shortImage

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

2024-07-15 Thread via GitHub
ppkarwasz commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1677494926 ## src/site/antora/modules/ROOT/examples/manual/lookups/MainArgsExample.java: ## @@ -0,0 +1,43 @@ +/* + * Licensed to the Apache Software Foundation (ASF) unde

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

2024-07-15 Thread via GitHub
sylphrena0 commented on issue #391: URL: https://github.com/apache/logging-log4cxx/issues/391#issuecomment-2228605868 I am using the configuration from the example, so the naming is correct. For the example, the macro is `IMPLEMENT_LOG4CXX_OBJECT(NullWriterAppender)` and the xml is:

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

2024-07-15 Thread via GitHub
rm5248 commented on issue #391: URL: https://github.com/apache/logging-log4cxx/issues/391#issuecomment-2229703108 If you've tried that, the only other thing that I can think of is that the class might not be registering properly with log4cxx - this depends slightly on how log4cxx is built/

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

2024-07-15 Thread via GitHub
swebb2066 commented on issue #391: URL: https://github.com/apache/logging-log4cxx/issues/391#issuecomment-2229718788 The example `custom-appender` is build by the Log4cxx build scripts (unless you define `BUILD_TESTING=off`). Please try running that program by doing: ``` $ ( cd /home/

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

2024-07-15 Thread via GitHub
swebb2066 merged PR #392: URL: https://github.com/apache/logging-log4cxx/pull/392 -- 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 the specific comment. To unsubscribe, e-mail: notifications-unsubscr

Re: [I] RollingRandomAccessFile won't ZIP logs if there are 2 RRAF appenders (logging-log4j2)

2024-07-15 Thread via GitHub
github-actions[bot] closed issue #1804: RollingRandomAccessFile won't ZIP logs if there are 2 RRAF appenders URL: https://github.com/apache/logging-log4j2/issues/1804 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

Re: [I] Issue with logs being stopped getting generated at midnight while using date based rollover strategy in log4j2 (logging-log4j2)

2024-07-15 Thread via GitHub
github-actions[bot] closed issue #2010: Issue with logs being stopped getting generated at midnight while using date based rollover strategy in log4j2 URL: https://github.com/apache/logging-log4j2/issues/2010 -- This is an automated message from the Apache Git Service. To respond to the messa

[PR] Update macOS hosted runner versions used by CI [logging-log4cxx]

2024-07-15 Thread via GitHub
swebb2066 opened a new pull request, #393: URL: https://github.com/apache/logging-log4cxx/pull/393 Accoring to [this post](https://github.blog/changelog/2024-01-30-github-actions-macos-14-sonoma-is-now-available/), macOS 14 has been available since January -- This is an automated message

Re: [PR] Update macOS hosted runner versions used by CI [logging-log4cxx]

2024-07-15 Thread via GitHub
swebb2066 merged PR #393: URL: https://github.com/apache/logging-log4cxx/pull/393 -- 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 the specific comment. To unsubscribe, e-mail: notifications-unsubscr

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

2024-07-16 Thread via GitHub
vy commented on code in PR #2736: URL: https://github.com/apache/logging-log4j2/pull/2736#discussion_r1679076913 ## src/site/antora/modules/ROOT/examples/manual/lookups/MainArgsExample.java: ## @@ -0,0 +1,43 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one o

<    16   17   18   19   20   21   22   23   24   25   >