[jira] [Commented] (LOG4J2-3424) JDBC Appender configuration properties not handled correctly after upgrading to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501202#comment-17501202 ] Grzegorz Grzybek commented on LOG4J2-3424: -- Thank you for your quick response a

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501191#comment-17501191 ] Piotr P. Karwasz commented on LOG4J2-3423: -- I think some refactoring is require

[GitHub] [logging-log4j2] rtlusty closed pull request #780: LOG4J2-3423 - Prevent unclosed JAR file containing Log4j configuration

rtlusty closed pull request #780: URL: https://github.com/apache/logging-log4j2/pull/780 -- 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: notificat

[GitHub] [logging-log4j2] rtlusty commented on pull request #780: LOG4J2-3423 - Prevent unclosed JAR file containing Log4j configuration

rtlusty commented on pull request #780: URL: https://github.com/apache/logging-log4j2/pull/780#issuecomment-1058887365 Better option for the fix has been provided. Closing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501186#comment-17501186 ] Radim Tlusty commented on LOG4J2-3423: -- [~rgoers]  Thanks. According to my tests,

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501168#comment-17501168 ] ASF subversion and git services commented on LOG4J2-3423: - Commi

[jira] [Commented] (LOG4J2-3424) JDBC Appender configuration properties not handled correctly after upgrading to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501171#comment-17501171 ] Ralph Goers commented on LOG4J2-3424: - We would have to do something similar to what

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501169#comment-17501169 ] Ralph Goers commented on LOG4J2-3423: - I've added a fix based on the workaround list

[GitHub] [logging-log4j2] carterkozak commented on pull request #783: LOG4J2-3424: Correctly handle property attribute values

carterkozak commented on pull request #783: URL: https://github.com/apache/logging-log4j2/pull/783#issuecomment-1058805314 planning to clean this up and fix revapi tomorrow -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1750#comment-1750 ] Ralph Goers commented on LOG4J2-3425: - If the appender configuration doesn't have to

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #783: LOG4J2-3424: Correctly handle property attribute values

carterkozak commented on a change in pull request #783: URL: https://github.com/apache/logging-log4j2/pull/783#discussion_r819221798 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/config/Property.java ## @@ -118,15 +119,36 @@ public static Property create

[GitHub] [logging-log4j2] carterkozak opened a new pull request #783: LOG4J2-3424: Correctly handle property attribute values

carterkozak opened a new pull request #783: URL: https://github.com/apache/logging-log4j2/pull/783 This fixes handling of properties in .properties configurations as well as those defined using `` which are parsed slightly differently from those which use the `value` syntax. -- T

[jira] [Commented] (LOG4J2-3424) JDBC Appender configuration properties not handled correctly after upgrading to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501099#comment-17501099 ] Carter Kozak commented on LOG4J2-3424: -- Ouch, I see the cause, still looking into w

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501079#comment-17501079 ] Piotr P. Karwasz edited comment on LOG4J2-3423 at 3/3/22, 11:22 PM: --

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501079#comment-17501079 ] Piotr P. Karwasz commented on LOG4J2-3423: -- Undertow had the same issue (cf. [

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501073#comment-17501073 ] Ralph Goers edited comment on LOG4J2-3423 at 3/3/22, 11:12 PM: ---

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501073#comment-17501073 ] Ralph Goers edited comment on LOG4J2-3423 at 3/3/22, 11:15 PM: ---

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501073#comment-17501073 ] Ralph Goers commented on LOG4J2-3423: - Hmm. I thought I tried to avoid using a URLCo

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501038#comment-17501038 ] Gary D. Gregory commented on LOG4J2-3423: - I wonder if there is a JDK bug for th

[jira] [Reopened] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiří Smolík reopened LOG4J2-3425: - > Syslog appender lacks the SocketOptions setting > ---

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500984#comment-17500984 ] Jiří Smolík commented on LOG4J2-3425: - [~ggregory]  When I find some time, I will t

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500956#comment-17500956 ] Jiří Smolík commented on LOG4J2-3425: - In the short term, SocketChannelAppender is l

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500951#comment-17500951 ] Gary D. Gregory commented on LOG4J2-3425: - Hm, do we want a new {{SocketChannelA

[jira] [Updated] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3425: External issue URL: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4031100 > Syslog

[jira] [Reopened] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Tlusty reopened LOG4J2-3423: -- I like the solution with {{setUseCaches(false)}} and it resolves the problem with closing of the

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500937#comment-17500937 ] Ralph Goers commented on LOG4J2-3425: - I actually experienced this very problem with

[jira] [Updated] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3425: Summary: Syslog appender lacks the SocketOptions setting (was: Syslog appender lacks the

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500899#comment-17500899 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 5:04 PM:

[jira] [Resolved] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3425. - Fix Version/s: 2.17.3 Resolution: Fixed > Syslog appender lacks the SocketOptions

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500899#comment-17500899 ] Gary D. Gregory commented on LOG4J2-3425: - [~SkyCrawl]  Dang it, well that's la

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the SocketOptions setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500895#comment-17500895 ] ASF subversion and git services commented on LOG4J2-3425: - Commi

[jira] [Commented] (LOG4J2-3424) JDBC Appender configuration properties not handled correctly after upgrading to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500887#comment-17500887 ] Gary D. Gregory commented on LOG4J2-3424: - [~ckozak] Any advice? It looks like r

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500866#comment-17500866 ] Gary D. Gregory edited comment on LOG4J2-3423 at 3/3/22, 4:48 PM:

[jira] [Updated] (LOG4J2-3360) Document unsafe lookup usage patterns

[ https://issues.apache.org/jira/browse/LOG4J2-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3360: Fix Version/s: 2.17.3 (was: 2.17.2) > Document unsafe lookup usage

[jira] [Updated] (LOG4J2-3340) StatusLogger's log Level cannot be changed as advertised

[ https://issues.apache.org/jira/browse/LOG4J2-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3340: Fix Version/s: 2.17.3 (was: 2.17.2) > StatusLogger's log Level cann

[jira] [Resolved] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3423. - Fix Version/s: 2.17.3 Resolution: Fixed Fixed in git branch {{release-2.x}} and M

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500864#comment-17500864 ] ASF subversion and git services commented on LOG4J2-3423: - Commi

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500855#comment-17500855 ] Jiří Smolík commented on LOG4J2-3425: - {noformat} Also, do not use 2.12.1, use at le

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500846#comment-17500846 ] Jiří Smolík commented on LOG4J2-3425: - Probably due to this line: [https://github.c

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500840#comment-17500840 ] Jiří Smolík commented on LOG4J2-3425: - [~ggregory]  I tried the following configura

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500826#comment-17500826 ] ASF subversion and git services commented on LOG4J2-3423: - Commi

[jira] [Work started] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3423 started by Gary D. Gregory. --- > JAR file containing Log4j configuration isn't closed >

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500782#comment-17500782 ] Piotr P. Karwasz commented on LOG4J2-3423: -- There are two problems with {{JarUR

[GitHub] [logging-log4j2] turesheim commented on pull request #782: Improve error message when k8s pod could not be located

turesheim commented on pull request #782: URL: https://github.com/apache/logging-log4j2/pull/782#issuecomment-1058086473 I did at first simply logg the exception – but it got eaten by some Wildfly stuff where I was testing this, hence adding the Exception message to the log message. --

[jira] [Assigned] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3423: --- Assignee: Gary D. Gregory > JAR file containing Log4j configuration isn't closed >

[jira] [Comment Edited] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500693#comment-17500693 ] Gary D. Gregory edited comment on LOG4J2-3423 at 3/3/22, 2:05 PM:

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500747#comment-17500747 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 1:50 PM:

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500764#comment-17500764 ] Jiří Smolík commented on LOG4J2-3425: - Ah, I completely missed that. Thank you. I s

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500747#comment-17500747 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 1:29 PM:

[jira] [Comment Edited] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500747#comment-17500747 ] Gary D. Gregory edited comment on LOG4J2-3425 at 3/3/22, 1:30 PM:

[jira] [Commented] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500747#comment-17500747 ] Gary D. Gregory commented on LOG4J2-3425: - [~SkyCrawl]  A Syslog Appender is a

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500693#comment-17500693 ] Gary D. Gregory commented on LOG4J2-3423: - The url connection's setUseCaches can

[jira] [Commented] (LOG4J2-3419) Unable to create custom logging level using log4j 2 Bridge API

[ https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500686#comment-17500686 ] Gary D. Gregory commented on LOG4J2-3419: - [~ragini]  See my first comment and

[GitHub] [logging-log4j2] garydgregory commented on pull request #782: Improve error message when k8s pod could not be located

garydgregory commented on pull request #782: URL: https://github.com/apache/logging-log4j2/pull/782#issuecomment-1057957470 I don't see why we don't log the exception, @rgoers ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[jira] [Updated] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiří Smolík updated LOG4J2-3425: Description: Recently, we've had an issue with our syslog server (collector), where it was sudden

[jira] [Updated] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiří Smolík updated LOG4J2-3425: Description: Recently, we've had an issue with our syslog server (collector), where it was sudden

[jira] [Updated] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

[ https://issues.apache.org/jira/browse/LOG4J2-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiří Smolík updated LOG4J2-3425: Description: Recently, we've had an issue with our syslog server (collector), where it was sudden

[jira] [Created] (LOG4J2-3425) Syslog appender lacks the 'readTimeoutMillis' setting

Jiří Smolík created LOG4J2-3425: --- Summary: Syslog appender lacks the 'readTimeoutMillis' setting Key: LOG4J2-3425 URL: https://issues.apache.org/jira/browse/LOG4J2-3425 Project: Log4j 2 Issue T

[jira] [Commented] (LOG4J2-3423) JAR file containing Log4j configuration isn't closed

[ https://issues.apache.org/jira/browse/LOG4J2-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500664#comment-17500664 ] Radim Tlusty commented on LOG4J2-3423: -- It's rather a weird design of the {{{}URLCo

[jira] [Commented] (LOG4J2-3416) Line Number Not getting printeed

[ https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500574#comment-17500574 ] Sagar Salal commented on LOG4J2-3416: - Yes please whenever you get time please help