[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005890#comment-16005890
]
clonline commented on LOG4J2-1904:
--
You mean if I override the SyslogLayout and Rfc5424L
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005836#comment-16005836
]
Ralph Goers edited comment on LOG4J2-1904 at 5/11/17 3:36 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1904.
-
Resolution: Not A Problem
The default layout(s) for the syslog appender are the SyslogLayout and
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1904:
Description:
Hello
The following is my settings.
{code}
{code}
But the facility received
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1904:
Description:
Hello
The following is my settings.
{code}
{code}
But the facility received
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1904:
Description:
Hello
The following is my settings.
But the facility received by rsyslog i
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005833#comment-16005833
]
clonline commented on LOG4J2-1904:
--
If I delete ,LOCAL6 will be received by rsyslog.
>
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clonline updated LOG4J2-1904:
-
Description:
Hello
The following is my settings.
But the facility received by rsyslog is not L
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clonline updated LOG4J2-1904:
-
Comment: was deleted
(was: Hello
The following is my settings.
But the facility receive
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clonline updated LOG4J2-1904:
-
Affects Version/s: 2.8.2
Component/s: Layouts
Issue Type: Question (was: Bug)
> fac
[
https://issues.apache.org/jira/browse/LOG4J2-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005133#comment-16005133
]
Gary Gregory commented on LOG4J2-1389:
--
We are working toward having an SPI package
[
https://issues.apache.org/jira/browse/LOG4J2-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1905:
-
Priority: Major (was: Critical)
Changing priority from 'Critical' to 'Major'.
> file resources
[
https://issues.apache.org/jira/browse/LOG4J2-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005033#comment-16005033
]
Rafal Foltynski commented on LOG4J2-1389:
-
[~garydgregory] this argument seems to
[
https://issues.apache.org/jira/browse/LOG4J2-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Santos updated LOG4J2-1906:
Description:
The DirectWriteRolloverStrategy is not properly determining the filename of the
new l
https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/config/AppenderControl.java
All appenders are supported generically.
On 10 May 2017 at 09:59, Mikael Ståldal wrote:
> Do we have recursion prevention in any other appender than KafkaAppen
[
https://issues.apache.org/jira/browse/LOG4J2-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004826#comment-16004826
]
Matt Sicker commented on LOG4J2-1905:
-
There are several ways to do that already. The
Do we have recursion prevention in any other appender than KafkaAppender?
On Wed, May 10, 2017 at 4:55 PM, Matt Sicker wrote:
> We already have recursion prevention in appenders, so that's not an issue.
> Runtime cycles are based on module imports apparently, not necessarily on
> the flow of dat
We already have recursion prevention in appenders, so that's not an issue.
Runtime cycles are based on module imports apparently, not necessarily on
the flow of data.
On 10 May 2017 at 04:28, Mikael Ståldal wrote:
> Actually, it is a bit of a problem that the Kafka client library do logging
> du
[
https://issues.apache.org/jira/browse/LOG4J2-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Santos updated LOG4J2-1906:
Description:
The DirectWriteRolloverStrategy is not properly determining the filename of the
new l
João Santos created LOG4J2-1906:
---
Summary: DirectWriteRolloverStrategy not properly creating files
Key: LOG4J2-1906
URL: https://issues.apache.org/jira/browse/LOG4J2-1906
Project: Log4j 2
Issue
tsimba kely created LOG4J2-1905:
---
Summary: file resources in property substitution
Key: LOG4J2-1905
URL: https://issues.apache.org/jira/browse/LOG4J2-1905
Project: Log4j 2
Issue Type: New Featu
It will require that modules that have Log4J plugins declare the package
containing the plugins as "open" to Log4J. Apparently we will also have to
call Module.addReads() to be able to access the module.
Ralph
Sent from my iPad
> On May 10, 2017, at 2:40 AM, Mikael Ståldal wrote:
>
> As fa
As far as I can see, we use setAccessible in our plugin loader? Can that be
a problem?
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-May/012571.html
On Wed, May 10, 2017 at 6:34 AM, Ralph Goers
wrote:
> I got further clarification on the jigsaw dev list.
> http://mail.openjdk.java.net/
Actually, it is a bit of a problem that the Kafka client library do logging
during our calls to it in KafkaAppender. But this is only a problem at
runtime.
On Tue, May 9, 2017 at 6:36 PM, Ralph Goers
wrote:
> As I understand it, what you are saying is possible but Log4j doesn’t
> currently need
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clonline updated LOG4J2-1904:
-
Summary: facility setted to syslogappendar don't work,but user facility is
being used. (was: facility se
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004241#comment-16004241
]
clonline edited comment on LOG4J2-1904 at 5/10/17 8:00 AM:
---
Hel
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004241#comment-16004241
]
clonline edited comment on LOG4J2-1904 at 5/10/17 7:56 AM:
---
The
[
https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004241#comment-16004241
]
clonline commented on LOG4J2-1904:
--
The following is my settings.
But t
clonline created LOG4J2-1904:
Summary: facility setted to syslogappendar don't work,but user
facility is working
Key: LOG4J2-1904
URL: https://issues.apache.org/jira/browse/LOG4J2-1904
Project: Log4j 2
29 matches
Mail list logo
