swebb2066 commented on PR #381:
URL: https://github.com/apache/logging-log4cxx/pull/381#issuecomment-2097162272
Also need a test case for telnetappender and socketappender
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2096837528
It does look similar. I think with the changes I mentioned i am actually all
set. I don’t see the warnings on successful rolling that a file is already
open, and I d
marcreichman-pfi closed issue #2566: When logging from multiple threads, an
appender can be broken until app restart if it rolls over
URL: https://github.com/apache/logging-log4j2/issues/2566
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
ppkarwasz commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2096782770
I really ought to look deeper into GlassFish.
The `log4j-jakarta-web` should not create a new logger context **unless**
the classloader returned by `ServletContext#ge
dependabot[bot] opened a new pull request, #143:
URL: https://github.com/apache/logging-log4j-audit/pull/143
Bumps
[org.apache.maven.plugin-tools:maven-plugin-annotations](https://github.com/apache/maven-plugin-tools)
from 3.11.0 to 3.13.0.
Release notes
Sourced from https://githu
dependabot[bot] closed pull request #136: Bump
org.apache.maven.plugin-tools:maven-plugin-annotations from 3.11.0 to 3.12.0
URL: https://github.com/apache/logging-log4j-audit/pull/136
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
dependabot[bot] commented on PR #136:
URL:
https://github.com/apache/logging-log4j-audit/pull/136#issuecomment-2096469649
Superseded by #143.
--
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
dependabot[bot] closed pull request #135: Bump
org.apache.maven.plugin-tools:maven-plugin-tools-api from 3.11.0 to 3.12.0
URL: https://github.com/apache/logging-log4j-audit/pull/135
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
dependabot[bot] commented on PR #135:
URL:
https://github.com/apache/logging-log4j-audit/pull/135#issuecomment-2096465485
Superseded by #142.
--
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
dependabot[bot] opened a new pull request, #142:
URL: https://github.com/apache/logging-log4j-audit/pull/142
Bumps
[org.apache.maven.plugin-tools:maven-plugin-tools-api](https://github.com/apache/maven-plugin-tools)
from 3.11.0 to 3.13.0.
Release notes
Sourced from https://github.
rm5248 commented on PR #381:
URL: https://github.com/apache/logging-log4cxx/pull/381#issuecomment-2096202951
The updates make me think that maybe we should have a CI action that builds
with the events at exit feature configured to be on to make sure it all builds.
--
This is an automated
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2096127506
@ppkarwasz I have a couple new findings, which may make sense to you, but at
the very least I'll try a new configuration and see how it goes. I was able to
dig in a
github-actions[bot] merged PR #46:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/46
--
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: not
github-actions[bot] merged PR #46:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/46
--
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: not
dependabot[bot] closed pull request #42: Bump com.fasterxml.jackson:jackson-bom
from 2.16.2 to 2.17.0
URL: https://github.com/apache/logging-log4j-audit-sample/pull/42
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
dependabot[bot] commented on PR #42:
URL:
https://github.com/apache/logging-log4j-audit-sample/pull/42#issuecomment-2095802980
Superseded by #46.
--
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
dependabot[bot] opened a new pull request, #46:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/46
Bumps
[com.fasterxml.jackson:jackson-bom](https://github.com/FasterXML/jackson-bom)
from 2.16.2 to 2.17.1.
Commits
https://github.com/FasterXML/jackson-bom/commit/
github-actions[bot] merged PR #2569:
URL: https://github.com/apache/logging-log4j2/pull/2569
--
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: notificatio
github-actions[bot] merged PR #174:
URL: https://github.com/apache/logging-parent/pull/174
--
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
github-actions[bot] merged PR #175:
URL: https://github.com/apache/logging-parent/pull/175
--
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
vy commented on issue #2169:
URL:
https://github.com/apache/logging-log4j2/issues/2169#issuecomment-209305
@shloim, any updates? Were you able to reproduce the issue with Log4j
`2.23.1` using Disruptor 4?
--
This is an automated message from the Apache Git Service.
To respond to the
vy commented on issue #2169:
URL:
https://github.com/apache/logging-log4j2/issues/2169#issuecomment-2095553249
> Perhaps the [Log4j async
manual](https://logging.apache.org/log4j/2.x/manual/async.html) could be more
clear
We can indeed do this. Updated the #2534 description accordi
github-actions[bot] merged PR #119:
URL: https://github.com/apache/logging-log4j-tools/pull/119
--
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
mpv945 closed issue #2453: spring boot 3.2.4 + spring-boot-starter-log4j2 +
spring-boot-starter-undertow
URL: https://github.com/apache/logging-log4j2/issues/2453
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
24 matches
Mail list logo
