FYI, this alpha uses Log4j 2.
Gary
From: Oleg Kalnichevski
Sent: Thursday, May 11, 2017 5:54:27 AM
To: annou...@apache.org; priv...@hc.apache.org; d...@hc.apache.org;
httpclient-us...@hc.apache.org
Subject: [ANNOUNCEMENT] HttpComponents Client 5.0 alpha2 release
[
https://issues.apache.org/jira/browse/LOG4J2-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006495#comment-16006495
]
Mikael Ståldal commented on LOG4J2-1797:
It would also be useful to be able to ha
https://issues.apache.org/jira/browse/LOG4J2-1797
Added comment.
On Thu, May 11, 2017 at 4:11 PM, Matt Sicker wrote:
> So this is something to consider with an async appender API. I don't
> remember the ticket number, but there's one about such an API, and handling
> recursive logging may be ha
So this is something to consider with an async appender API. I don't
remember the ticket number, but there's one about such an API, and handling
recursive logging may be handled more generically in such an API.
On 11 May 2017 at 07:58, Mikael Ståldal wrote:
> The Kafka client library spawns its
[
https://issues.apache.org/jira/browse/LOG4J2-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006364#comment-16006364
]
ASF subversion and git services commented on LOG4J2-1903:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006363#comment-16006363
]
ASF subversion and git services commented on LOG4J2-1896:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006361#comment-16006361
]
ASF subversion and git services commented on LOG4J2-1900:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006362#comment-16006362
]
ASF subversion and git services commented on LOG4J2-1899:
-
Commit
The Kafka client library spawns its own threads, so this recursive logging
is most likely done on another thread. That explains why the
AppenderControl prevention does not work.
So we should keep the prevention in KafkaAppender.
On Thu, May 11, 2017 at 2:50 PM, Apache wrote:
> How does Appender
How does AppenderControl not prevent recursive logging? If the appender gets
called a second time on the thread then it will ignore the event. If the
appender or Kafka are creating new threads that are logging then you could get
the behavior you mention, but I don't see how that could be handle
The Kafka appender uses the Kafka client library, and that client library
does it's own logging through SLF4J, it always emits a few log messages at
DEBUG level on each message sent.
If you have log4j-slf4j-impl in classpath and enable DEBUG logging through
KafkaAppender, you will get recursive lo
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tsimba kely updated LOG4J2-1904:
Comment: was deleted
(was: i just write a custom layout to resolve this problem. I spent a days to
Starting a new thread about recursive logging at runtime since that's not
related to Java 9 modules.
On Wed, May 10, 2017 at 5:08 PM, Matt Sicker wrote:
> https://github.com/apache/logging-log4j2/blob/master/
> log4j-core/src/main/java/org/apache/logging/log4j/core/
> config/AppenderControl.java
Remko Popma created LOG4J2-1908:
---
Summary: Cryptic error message when misconfigured
Key: LOG4J2-1908
URL: https://issues.apache.org/jira/browse/LOG4J2-1908
Project: Log4j 2
Issue Type: Improvem
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006180#comment-16006180
]
tsimba kely edited comment on LOG4J2-1904 at 5/11/17 10:03 AM:
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006180#comment-16006180
]
tsimba kely commented on LOG4J2-1904:
-
i just write a custom layout to resolve this p
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tsimba kely updated LOG4J2-1904:
Comment: was deleted
(was: for that , you should write an custom pattern layout(same as
patternLay
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006173#comment-16006173
]
clonline commented on LOG4J2-1904:
--
>I'll doing to resolve this problem of syslog Layout
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006020#comment-16006020
]
tsimba kely commented on LOG4J2-1904:
-
for that , you should write an custom pattern
tsimba kely created LOG4J2-1907:
---
Summary: file resources as a property
Key: LOG4J2-1907
URL: https://issues.apache.org/jira/browse/LOG4J2-1907
Project: Log4j 2
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LOG4J2-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tsimba kely closed LOG4J2-1905.
---
Resolution: Won't Do
> file resources in property substitution
>
21 matches
Mail list logo
