swebb2066 commented on PR #372:
URL: https://github.com/apache/logging-log4cxx/pull/372#issuecomment-2074155378
The [1.3.0 staging web
site](https://logging.staged.apache.org/log4cxx/1.3.0) is available for review.
--
This is an automated message from the Apache Git Service.
To respond to
swebb2066 commented on issue #370:
URL:
https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2074087961
> Pages I cited are implemented in a project agnostic way.
They really do not read like that. They are heavily oriented towards Log4j.
> The goal is to
>
swebb2066 opened a new pull request, #372:
URL: https://github.com/apache/logging-log4cxx/pull/372
This PR adds links as requested in #370
--
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
github-actions[bot] merged PR #53:
URL: https://github.com/apache/logging-log4j-scala/pull/53
--
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: notificati
swebb2066 commented on code in PR #369:
URL: https://github.com/apache/logging-log4cxx/pull/369#discussion_r1577072840
##
src/main/cpp/filewatchdog.cpp:
##
@@ -74,11 +74,7 @@ void FileWatchdog::stop()
{
LogLog::debug(LOG4CXX_STR("Stopping file watchdog"));
m_pri
github-actions[bot] merged PR #131:
URL: https://github.com/apache/logging-log4j-samples/pull/131
--
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: notifi
github-actions[bot] merged PR #101:
URL: https://github.com/apache/logging-log4j-transform/pull/101
--
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: noti
JamesChambers-E11074 commented on issue #1795:
URL:
https://github.com/apache/logging-log4j2/issues/1795#issuecomment-2072923267
That works. If you ever want to reproduce it, simply run the code on zOS
add a compress step and then look at the final ZIP.
From: Piotr P. Karwasz ***@**
jolly28 commented on issue #2414:
URL:
https://github.com/apache/logging-log4j2/issues/2414#issuecomment-2072811890
@vy I have used the latest log4j-api and log4j-core jars (2.24.0-SNAPSHOT).
seems the issue is solved.
--
This is an automated message from the Apache Git Service.
To r
ppkarwasz commented on issue #1795:
URL:
https://github.com/apache/logging-log4j2/issues/1795#issuecomment-2072333009
Thanks for the fast answer.
I am closing this issue then, since we are unable to reproduce it.
--
This is an automated message from the Apache Git Service.
To respo
ppkarwasz closed issue #1795: Issue with Log4J2 Compression/Decompression on
the Mainframe
URL: https://github.com/apache/logging-log4j2/issues/1795
--
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 t
ppkarwasz commented on issue #2462:
URL:
https://github.com/apache/logging-log4j2/issues/2462#issuecomment-2072329175
Fixed by #2468
--
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
ppkarwasz closed issue #2462: Provide a programmatic way to enable/disable
log4j2 JMX beans creation
URL: https://github.com/apache/logging-log4j2/issues/2462
--
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
ppkarwasz closed issue #2318: [Fatal Error] log4j2.yml:1:1: Content is not
allowed in prolog.
URL: https://github.com/apache/logging-log4j2/issues/2318
--
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 t
ppkarwasz closed issue #2131: Split CLI commands from `log4j-1.2-api` and
`log4j-core`
URL: https://github.com/apache/logging-log4j2/issues/2131
--
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 s
ppkarwasz commented on issue #2131:
URL:
https://github.com/apache/logging-log4j2/issues/2131#issuecomment-2072312141
Closed in #2435
--
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
FreeAndNil commented on issue #142:
URL:
https://github.com/apache/logging-log4net/issues/142#issuecomment-2072310135
@SwEngine is this still relevant for you?
Otherwise I will close this at the end of the week.
--
This is an automated message from the Apache Git Service.
To respond to
ppkarwasz closed issue #2106: Consider moving recyclers to `log4j-core`
URL: https://github.com/apache/logging-log4j2/issues/2106
--
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.
ppkarwasz closed issue #2100: Document Log4j security model
URL: https://github.com/apache/logging-log4j2/issues/2100
--
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 unsubsc
ppkarwasz commented on issue #2074:
URL:
https://github.com/apache/logging-log4j2/issues/2074#issuecomment-2072301269
@marinesky,
The GC log you attached doesn't point to any error condition. What problems
are you experiencing?
--
This is an automated message from the Apache Git S
JamesChambers-E11074 commented on issue #1795:
URL:
https://github.com/apache/logging-log4j2/issues/1795#issuecomment-2072241469
The mainframe uses a different character set (CP1047) when creating files.
Creating a ZIP of those files puts them in a state where I cannot unzip them.
I have
castriottaa commented on issue #1958:
URL:
https://github.com/apache/logging-log4j2/issues/1958#issuecomment-2072214067
@ppkarwasz My application is a batch that starts every day on event.
Probably you are right: that configuration is missing.
If you confirm that it manages the rollove
ppkarwasz commented on issue #2027:
URL:
https://github.com/apache/logging-log4j2/issues/2027#issuecomment-2072210074
This should be fixed by #2469
--
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 t
ppkarwasz closed issue #2022: Various tests abuse static state that no longer
works
URL: https://github.com/apache/logging-log4j2/issues/2022
--
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 spec
ppkarwasz commented on issue #2022:
URL:
https://github.com/apache/logging-log4j2/issues/2022#issuecomment-2072204542
They seem to be fixed now.
--
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 t
ppkarwasz closed issue #2007: Log4j2 starts again after LogManager.shutdown()
URL: https://github.com/apache/logging-log4j2/issues/2007
--
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
ppkarwasz commented on issue #1958:
URL:
https://github.com/apache/logging-log4j2/issues/1958#issuecomment-2072190413
@castriottaa,
Does your application run 24/7 or do you restart it every day?
In the latter case you might be missing an
[`OnStartupTriggeringPolicy`](https://loggi
ppkarwasz commented on issue #1804:
URL:
https://github.com/apache/logging-log4j2/issues/1804#issuecomment-2072176344
@JohnLussmyer,
Sorry for the late answer. In your configuration file I see only one
`RollingFileAppender`, could you provide the whole configuration file?
--
This
ppkarwasz commented on issue #1795:
URL:
https://github.com/apache/logging-log4j2/issues/1795#issuecomment-2072168855
Hi @JamesChambers-E11074,
Could you provide an excerpt of your Log4j configuration file?
--
This is an automated message from the Apache Git Service.
To respond to
ppkarwasz closed issue #1783: SpringProfile arbiter fails without a Spring's
environment
URL: https://github.com/apache/logging-log4j2/issues/1783
--
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
swebb2066 opened a new pull request, #371:
URL: https://github.com/apache/logging-log4cxx/pull/371
(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 unsubscri
ppkarwasz closed issue #1311: java.lang.NoClassDefFoundError: Failed resolution
of: Lorg/apache/logging/log4j/core/lookup/StrLookup
URL: https://github.com/apache/logging-log4j2/issues/1311
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
ppkarwasz commented on issue #1311:
URL:
https://github.com/apache/logging-log4j2/issues/1311#issuecomment-2072121185
@akash-queuebuster,
This seems to be a simple classpath problem in your application, not a
problem with Log4j.
If you think otherwise, feel free to reopen this iss
ppkarwasz closed issue #1229: JMX should be disabled by default
URL: https://github.com/apache/logging-log4j2/issues/1229
--
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 uns
ppkarwasz opened a new pull request, #2500:
URL: https://github.com/apache/logging-log4j2/pull/2500
We add a GitHub action to automatically close GitHub issues that:
- are marked as `waiting-for-user`,
- have been inactive for more than 60 days.
--
This is an automated messag
vy commented on issue #2414:
URL:
https://github.com/apache/logging-log4j2/issues/2414#issuecomment-2072032310
@jolly28, pushed a small fix in f0bd87818d43efa8337f56526ced2020c308d9bf.
Could you see if the most recent `2.24.0-SNAPSHOT` solves the problem, please?
(Note that you need to [ad
ppkarwasz closed issue #1216: Refresh CONTRIBUTING.md
URL: https://github.com/apache/logging-log4j2/issues/1216
--
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,
github-actions[bot] merged PR #164:
URL: https://github.com/apache/logging-parent/pull/164
--
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
vopl commented on code in PR #369:
URL: https://github.com/apache/logging-log4cxx/pull/369#discussion_r1575988574
##
src/main/cpp/filewatchdog.cpp:
##
@@ -74,11 +74,7 @@ void FileWatchdog::stop()
{
LogLog::debug(LOG4CXX_STR("Stopping file watchdog"));
m_priv->in
vy commented on issue #2121:
URL:
https://github.com/apache/logging-log4j2/issues/2121#issuecomment-2071831349
Fixed in #2480 (`main`) and #2487 (`2.x`).
--
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
vy closed issue #2121: Java compatibility information is missing
URL: https://github.com/apache/logging-log4j2/issues/2121
--
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 un
vy closed issue #2063: `LevelResolver` of `JsonTemplateLayout` wrongly assumes
that `Level.values()` is constant
URL: https://github.com/apache/logging-log4j2/issues/2063
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
vy commented on issue #2063:
URL:
https://github.com/apache/logging-log4j2/issues/2063#issuecomment-2071825194
Fixed in e0a2bcb4dc4c475ec79bb8b7b876f46062579eef (`2.x`) and
97e441dd9ee4236fd1ba31bc373bebee483a2ddc (`main`).
--
This is an automated message from the Apache Git Service.
To
vy merged PR #2498:
URL: https://github.com/apache/logging-log4j2/pull/2498
--
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...@lo
vy commented on issue #370:
URL:
https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2071664759
> As far as I can see, those three pages do not seem to have anything that
is relevant to a Log4cxx user.
Pages I cited are implemented in a project agnostic way. That is,
vy commented on PR #2498:
URL: https://github.com/apache/logging-log4j2/pull/2498#issuecomment-2071650563
@aabmass, thanks so much! I will merge this once CI passes and `cherry-pick`
it to `main` too.
--
This is an automated message from the Apache Git Service.
To respond to the message,
vy commented on code in PR #2498:
URL: https://github.com/apache/logging-log4j2/pull/2498#discussion_r1575804018
##
src/changelog/.2.x.x/add_GcpLayout_tracing_support.xml:
##
@@ -0,0 +1,8 @@
+
+http://www.w3.org/2001/XMLSchema-instance";
+ xmlns="https://logging.apache.org
47 matches
Mail list logo
