[
https://issues.apache.org/jira/browse/LOG4J2-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405627#comment-17405627
]
Ralph Goers edited comment on LOG4J2-3151 at 8/27/21, 6:41 AM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405627#comment-17405627
]
Ralph Goers commented on LOG4J2-3151:
-
This is working correctly. The levels are def
[
https://issues.apache.org/jira/browse/LOG4J2-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-3151.
-
Resolution: Not A Bug
> Messages get logged at level OFF
>
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405617#comment-17405617
]
Ralph Goers commented on LOG4J2-3138:
-
Actually, I think it would be an interesting
[
https://issues.apache.org/jira/browse/LOG4J2-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405616#comment-17405616
]
Ralph Goers commented on LOG4J2-3152:
-
Although JsonLayout hasn't been formally depr
[
https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1191.
-
Resolution: Duplicate
> Log4j completely hangs in TcpSocketManager after a while...
> --
[
https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405614#comment-17405614
]
Ralph Goers commented on LOG4J2-1191:
-
I am marking this as a duplicate of LOG4J2-31
rm5248 commented on a change in pull request #68:
URL: https://github.com/apache/logging-log4cxx/pull/68#discussion_r697068021
##
File path: src/main/cpp/threadutility.cpp
##
@@ -0,0 +1,91 @@
+#include "log4cxx/helpers/threadutility.h"
+#include "log4cxx/private/log4cxx_private
garydgregory commented on a change in pull request #564:
URL: https://github.com/apache/logging-log4j2/pull/564#discussion_r697036474
##
File path: log4j-mongodb4/pom.xml
##
@@ -88,6 +88,17 @@
de.flapdoodle.embed.mongo
test
+
+ org.apache.logging.lo
garydgregory commented on pull request #564:
URL: https://github.com/apache/logging-log4j2/pull/564#issuecomment-906799734
> Hi team,
> Please have take a look to the new test case that i submitted. In that
test, i choose to use real MongoDB server instead of the Flapdoodle's embedded
M
garydgregory commented on a change in pull request #564:
URL: https://github.com/apache/logging-log4j2/pull/564#discussion_r697032754
##
File path: log4j-mongodb4/pom.xml
##
@@ -88,6 +88,17 @@
de.flapdoodle.embed.mongo
test
+
+ org.apache.logging.lo
redapel commented on pull request #564:
URL: https://github.com/apache/logging-log4j2/pull/564#issuecomment-906654798
Hi team,
Please have take a look to the new test case that i submitted. In that test,
i choose to use real MongoDB server instead of the Flapdoodle's embedded
MongoDB a
BUILD UNSTABLE
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/337/
Project:
release-2.x
Date of build:
Thu, 26 Aug 2021 14:22:50 +
Build duration:
1 hr 21 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s),
Andy Lehane created LOG4J2-3152:
---
Summary: JSONLayout - Add mechanism for registering additional
modules (i.e. JodaModule)
Key: LOG4J2-3152
URL: https://issues.apache.org/jira/browse/LOG4J2-3152
Project
[
https://issues.apache.org/jira/browse/LOG4J2-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405271#comment-17405271
]
Volkan Yazici commented on LOG4J2-3138:
---
Closing the ticket due to insufficient ju
[
https://issues.apache.org/jira/browse/LOG4J2-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici closed LOG4J2-3138.
-
Assignee: Volkan Yazici
> Define a custom model for a json layout for creating custom json logs
vy closed pull request #562:
URL: https://github.com/apache/logging-log4j2/pull/562
--
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 pull request #562:
URL: https://github.com/apache/logging-log4j2/pull/562#issuecomment-906468899
I have just skimmed over the changes and I am totally against this PR. We
already have 3 competing JSON layouts in the project: `GelfLayout`,
`JsonLayout`, and its successor `Js
[
https://issues.apache.org/jira/browse/LOG4J2-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nils Breunese updated LOG4J2-3151:
--
Description:
I am using the following Log4j API to log messages at a configurable level:
{code
[
https://issues.apache.org/jira/browse/LOG4J2-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405256#comment-17405256
]
Wojciech Zych commented on LOG4J2-2829:
---
[~okanarbik] Did you find any workaround/
Nils Breunese created LOG4J2-3151:
-
Summary: Messages get logged at level OFF
Key: LOG4J2-3151
URL: https://issues.apache.org/jira/browse/LOG4J2-3151
Project: Log4j 2
Issue Type: Bug
Affe
vy merged pull request #561:
URL: https://github.com/apache/logging-log4j2/pull/561
--
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-
[
https://issues.apache.org/jira/browse/LOG4J2-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici closed LOG4J2-3073.
-
> Issues using Lookup Plugin in Json Template Logging
>
[
https://issues.apache.org/jira/browse/LOG4J2-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405247#comment-17405247
]
Volkan Yazici commented on LOG4J2-3073:
---
I am closing this ticket since the report
[
https://issues.apache.org/jira/browse/LOG4J2-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici resolved LOG4J2-3073.
---
Resolution: Fixed
> Issues using Lookup Plugin in Json Template Logging
> --
[
https://issues.apache.org/jira/browse/LOG4J2-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici updated LOG4J2-3073:
--
Fix Version/s: 2.15.0
> Issues using Lookup Plugin in Json Template Logging
>
[
https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405199#comment-17405199
]
Wojciech Zych commented on LOG4J2-1191:
---
[~pueffl] Did you try set SoTimeout? Did
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici updated LOG4J2-3147:
--
Fix Version/s: 2.15.0
> Kuberenetes Lookup referring to wrong Spring classname
> -
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici closed LOG4J2-3147.
-
Resolution: Fixed
> Kuberenetes Lookup referring to wrong Spring classname
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici reopened LOG4J2-3147:
---
> Kuberenetes Lookup referring to wrong Spring classname
> -
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew McMahon closed LOG4J2-3147.
---
Merged to master and release-2.x branch
I'll wait for the next patch release :) Thanks
> Kuber
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici resolved LOG4J2-3147.
---
Resolution: Fixed
> Kuberenetes Lookup referring to wrong Spring classname
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici reassigned LOG4J2-3147:
-
Assignee: Volkan Yazici
> Kuberenetes Lookup referring to wrong Spring classname
>
vy commented on pull request #569:
URL: https://github.com/apache/logging-log4j2/pull/569#issuecomment-906164869
Thanks so much for the fix @maccamlc, I have cherry-picked this onto
`release-2.x`. Mind closing the JIRA ticket, please?
--
This is an automated message from the Apache Git S
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405020#comment-17405020
]
ASF subversion and git services commented on LOG4J2-3147:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405018#comment-17405018
]
ASF subversion and git services commented on LOG4J2-3147:
-
Commi
vy merged pull request #569:
URL: https://github.com/apache/logging-log4j2/pull/569
--
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-
rgoers commented on pull request #569:
URL: https://github.com/apache/logging-log4j2/pull/569#issuecomment-906161364
Having a PR on the release-2.x branch would be great! Otherwise I would have
to cherry-pick it from master.
--
This is an automated message from the Apache Git Service.
To
vy commented on pull request #558:
URL: https://github.com/apache/logging-log4j2/pull/558#issuecomment-906156252
@rahimalizada, I have fixed it. Thanks so much for the warning.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
39 matches
Mail list logo
