[jira] [Updated] (LOG4J2-3359) Facility and priority missing in Syslog message when Syslog log appender and pattern layout is used with log4j1-2 bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3359: -- Fix Version/s: 2.17.3 > Facility and priority missing in Syslog message when Syslog log appen

[jira] [Created] (LOG4J2-3447) Log4j 1.x 2.17.2 bridge - Synchronization issue in multithreading (Losing huge data in multithreading)

Pooja Pandey created LOG4J2-3447: Summary: Log4j 1.x 2.17.2 bridge - Synchronization issue in multithreading (Losing huge data in multithreading) Key: LOG4J2-3447 URL: https://issues.apache.org/jira/browse/LOG4J2-

[jira] [Work started] (LOG4J2-3359) Facility and priority missing in Syslog message when Syslog log appender and pattern layout is used with log4j1-2 bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3359 started by Piotr Karwasz. - > Facility and priority missing in Syslog message when Syslog log appender a

[jira] [Commented] (LOG4J2-3445) not able to deploy log4j 2.12.4 with jboss web-app (jersey issue)

[ https://issues.apache.org/jira/browse/LOG4J2-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512208#comment-17512208 ] Piotr Karwasz commented on LOG4J2-3445: --- [~rgoers], since version 2.14.2 is used e

[jira] [Resolved] (LOGCXX-550) Add ability to get thread name not just ID

[ https://issues.apache.org/jira/browse/LOGCXX-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton resolved LOGCXX-550. - Resolution: Fixed > Add ability to get thread name not just ID >

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17512151#comment-17512151 ] Ralph Goers commented on LOG4J2-3440: - I'd have a concern here as whatever we do it

[GitHub] [logging-log4j2] ppkarwasz opened a new pull request #807: [LOG4J2-3359] Adds Log4j 1.x specific syslog layout

ppkarwasz opened a new pull request #807: URL: https://github.com/apache/logging-log4j2/pull/807 Log4j 1.x always used the BSD syslog layout, but allowed for an internal layout to specify the _MESSAGE_ format. This PR adds a variant of the Log4j 2.x `SyslogLayout`, that emulates Log4

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17512040#comment-17512040 ] Gary D. Gregory commented on LOG4J2-3440: - It seems that we should do something

[jira] [Commented] (LOG4J2-3446) AGPBI: {"kind":"error","text":"MethodHandle.invoke and MethodHandle.invokeExact are only supported starting with Android O (--min-api 26)","sources":[{}],"tool":"D8"}

[ https://issues.apache.org/jira/browse/LOG4J2-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511995#comment-17511995 ] Matt Sicker commented on LOG4J2-3446: - I don't see any log4j-related stack trace the

[jira] (LOG4J2-3359) Facility and priority missing in Syslog message when Syslog log appender and pattern layout is used with log4j1-2 bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3359 ] Piotr Karwasz deleted comment on LOG4J2-3359: --- was (Author: pkarwasz): The correct formatting of custom Log4j 1.x level names in all appenders, requires a custom layout for the Log4j 1.x S

[jira] [Resolved] (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:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3436. --- Resolution: Duplicate [~ragini], Thanks for the configuration sample, which clarifies what i

[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&focusedCommentId=17511844#comment-17511844 ] Ragini Gawande commented on LOG4J2-3436: [~pkarwasz]  I tried the work around s

[jira] [Resolved] (LOG4J2-3445) not able to deploy log4j 2.12.4 with jboss web-app (jersey issue)

[ https://issues.apache.org/jira/browse/LOG4J2-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3445. - Resolution: Not A Bug > not able to deploy log4j 2.12.4 with jboss web-app (jersey issue) >

[jira] [Commented] (LOG4J2-3445) not able to deploy log4j 2.12.4 with jboss web-app (jersey issue)

[ https://issues.apache.org/jira/browse/LOG4J2-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511679#comment-17511679 ] Ralph Goers commented on LOG4J2-3445: - Log4j 2.14.2 is packaged as a Java multi-rele

[jira] [Closed] (LOG4J2-3444) Log4j 1.2 Unsupported Flagging by Nessus

[ https://issues.apache.org/jira/browse/LOG4J2-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-3444. --- Resolution: Won't Fix > Log4j 1.2 Unsupported Flagging by Nessus > -

[jira] [Commented] (LOG4J2-3444) Log4j 1.2 Unsupported Flagging by Nessus

[ https://issues.apache.org/jira/browse/LOG4J2-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511675#comment-17511675 ] Ralph Goers commented on LOG4J2-3444: - You contact "Log4j support" by sending emails