[jira] [Comment Edited] (LOG4J2-3436) Log4j 2 syslogAppender prints localhost.localdomain instead of actual hostname
[ https://issues.apache.org/jira/browse/LOG4J2-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516624#comment-17516624 ] Ragini Gawande edited comment on LOG4J2-3436 at 4/4/22 5:50 AM: Hi [~pkarwasz], My issue is solved in the latest snapshot version. Thanks for getting this solved. Before closing this issue can you help me with the date by which the final build of 2.17.3 will be released? Asking this because [https://logging.apache.org/log4j/2.x/download.html] still has 2.17.2 as latest log4j version was (Author: JIRAUSER285931): Hi [~pkarwasz], My issue is solved in the latest snapshot version. Thanks for getting this solved. Before closing this issue can you help me with the date by which the final build of 2.17.3 will be released? > Log4j 2 syslogAppender prints localhost.localdomain instead of actual hostname > -- > > Key: LOG4J2-3436 > URL: https://issues.apache.org/jira/browse/LOG4J2-3436 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders, Log4j 1.2 bridge > Environment: Using log4j 2 bridge API: snapshot version of 2.17.3 > log4j-1.2-api-2.17.3.jar >Reporter: Ragini Gawande >Assignee: Piotr Karwasz >Priority: Blocker > > We are trying to use syslogAppender for our logging but in the logs its > prints localhost.localdomain instead of actual hostname > <13>Mar 14 22:33:41 *localhost.localdomain* Main[6133] +05:30 2022 572 1 > com.test.common.logging.Test | FINE#com.test.common.logging.Level - Can > print FINE > <13>Mar 14 22:33:41 *localhost.localdomain* Main[6133] +05:30 2022 572 1 > com.test.common.logging.Test | INFO#com.test.common.logging.Level - Can > print Info > > Here we are using snapshot version of log4j 2.17.3 > This issue was not seen when using log4j 2.17.1 > > Additional info: > JDK 1.8 > -Dlog4j1.compatibility=true -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (LOG4J2-3436) Log4j 2 syslogAppender prints localhost.localdomain instead of actual hostname
[ https://issues.apache.org/jira/browse/LOG4J2-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516624#comment-17516624 ] Ragini Gawande commented on LOG4J2-3436: Hi [~pkarwasz], My issue is solved in the latest snapshot version. Thanks for getting this solved. Before closing this issue can you help me with the date by which the final build of 2.17.3 will be released? > Log4j 2 syslogAppender prints localhost.localdomain instead of actual hostname > -- > > Key: LOG4J2-3436 > URL: https://issues.apache.org/jira/browse/LOG4J2-3436 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders, Log4j 1.2 bridge > Environment: Using log4j 2 bridge API: snapshot version of 2.17.3 > log4j-1.2-api-2.17.3.jar >Reporter: Ragini Gawande >Assignee: Piotr Karwasz >Priority: Blocker > > We are trying to use syslogAppender for our logging but in the logs its > prints localhost.localdomain instead of actual hostname > <13>Mar 14 22:33:41 *localhost.localdomain* Main[6133] +05:30 2022 572 1 > com.test.common.logging.Test | FINE#com.test.common.logging.Level - Can > print FINE > <13>Mar 14 22:33:41 *localhost.localdomain* Main[6133] +05:30 2022 572 1 > com.test.common.logging.Test | INFO#com.test.common.logging.Level - Can > print Info > > Here we are using snapshot version of log4j 2.17.3 > This issue was not seen when using log4j 2.17.1 > > Additional info: > JDK 1.8 > -Dlog4j1.compatibility=true -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (LOG4J2-3440) Log4j 1.2 bridge getAllAppenders() returns null enumeration
[ https://issues.apache.org/jira/browse/LOG4J2-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3440 started by Piotr Karwasz. - > Log4j 1.2 bridge getAllAppenders() returns null enumeration > --- > > Key: LOG4J2-3440 > URL: https://issues.apache.org/jira/browse/LOG4J2-3440 > Project: Log4j 2 > Issue Type: Bug > Components: Log4j 1.2 bridge >Affects Versions: 2.17.2 >Reporter: Pablo Rogina >Assignee: Piotr Karwasz >Priority: Major > Fix For: 2.17.3 > > > Old application using Log4j 1.2.x relies on Logger.getAllAppenders() to > decide if Log4j it's already configured (returned Enumeration has at least 1 > appender) or not (empty returned Enumeration). > Some recent code audits mandate to remove log4j v1 component(s) and to > upgrade to latest 2.17.2 release, so we're using Log4j 1.2 Bridge to comply > and not to change application code. > However, we're facing the issue describe here [1] for > Logger.getRootLogger().getAllAppenders() although with latest Log4j release > 2.17.2 the issue seems to be that data structure aai is never updated with > the proper configured appenders, given that now most of the work happens in > the Log4j v2 Core implementation, thus using LoggerContext > [1] [java - Log4j getAllAppenders() returns null enumeration - Stack > Overflow|https://stackoverflow.com/questions/32864929/log4j-getallappenders-returns-null-enumeration] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [logging-log4j2] ppkarwasz opened a new pull request #813: [LOG4J2-3440] Synchronize Log4j 1.x and Log4j 2.x appenders
ppkarwasz opened a new pull request #813: URL: https://github.com/apache/logging-log4j2/pull/813 Forwards the `addAppender`, `callAppenders`, `getAllAppenders` and `getAppender` calls the the corresponding Log4j 2.x objects if Log4j 2.x Core is present. The `getAllAppenders` method only returns those appenders, which are attached to homonymous logger config and are native Log4j 1.x appenders. -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (LOG4J2-3453) Filters contains invalid attributes "onMatch", "onMismatch"
[
https://issues.apache.org/jira/browse/LOG4J2-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz reassigned LOG4J2-3453:
-
Assignee: Piotr Karwasz
> Filters contains invalid attributes "onMatch", "onMismatch"
> ---
>
> Key: LOG4J2-3453
> URL: https://issues.apache.org/jira/browse/LOG4J2-3453
> Project: Log4j 2
> Issue Type: Bug
>Reporter: LuNng Wang
>Assignee: Piotr Karwasz
>Priority: Major
> Fix For: 2.17.2
>
>
> The following is my log4j2.properties
> {code:java}
> appender.console.filter.1.type = Filters
> appender.console.filter.1.a.type = ThresholdFilter
> appender.console.filter.1.a.level = info
> appender.console.filter.1.b.type = RegexFilter
> appender.console.filter.1.b.regex = .*Thrift error occurred during processing
> of message.*
> appender.console.filter.1.b.onMatch = deny
> appender.console.filter.1.b.onMismatch = neutral
> {code}
> When I set 'log4j2.appender.event.filter.1.type = Filters', it will throw a
> `Filters contains invalid attributes "onMatch", "onMismatch"` error message.
> What is correctly conf?
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
