[jira] [Commented] (LOG4J2-3350) Routing appender does not expand nested variables

[ https://issues.apache.org/jira/browse/LOG4J2-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479138#comment-17479138 ] Stefano Maioli commented on LOG4J2-3350: Hi Gary, I had searched but found nothing. Read better

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #724: Bump maven-dependency-plugin from 3.0.2 to 3.2.0

dependabot[bot] opened a new pull request #724: URL: https://github.com/apache/logging-log4j2/pull/724 Bumps [maven-dependency-plugin](https://github.com/apache/maven-dependency-plugin) from 3.0.2 to 3.2.0. Commits

[CI][SUCCESS] Logging/log4j/release-2.x#771 back to normal

BUILD SUCCESS Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/771/ Project: release-2.x Date of build: Thu, 20 Jan 2022 01:19:11 + Build duration: 1 hr 9 min and counting JUnit Tests Name: (root) Failed: 0 test(s),

[GitHub] [logging-log4j2] ppkarwasz opened a new pull request #723: Fixes service file

ppkarwasz opened a new pull request #723: URL: https://github.com/apache/logging-log4j2/pull/723 The META-INF/services file used the old `javax` namespace, hence the `ServletContainerInitializer` was never detected. -- This is an automated message from the Apache Git Service. To respond

[GitHub] [logging-log4j2] rgoers commented on pull request #722: LOG4J2-3350: Evaluate configuration property substitutions eagerly

rgoers commented on pull request #722: URL: https://github.com/apache/logging-log4j2/pull/722#issuecomment-1017024373 Other than adding a couple of comments this looks good to me. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[CI][UNSTABLE] Logging/log4j/release-2.x#770 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/770/ Project: release-2.x Date of build: Wed, 19 Jan 2022 23:05:34 + Build duration: 1 hr 18 min and counting JUnit Tests Name: (root) Failed: 0 test(s),

[jira] [Resolved] (LOG4J2-1397) Support ByteBufferLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1397. - Resolution: Won't Fix > Support ByteBufferLayout > > >

[jira] [Commented] (LOG4J2-1397) Support ByteBufferLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479035#comment-17479035 ] Remko Popma commented on LOG4J2-1397: - Given that the original requester (Kirk Pepperdine) never

[jira] [Updated] (LOG4J2-3354) Publish an SBOM with Log4j

[ https://issues.apache.org/jira/browse/LOG4J2-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-3354: Description: Log4j should publish a software bill of materials (SBOM) on each release to enable

[jira] [Created] (LOG4J2-3354) Publish an SBOM with Log4j

Matt Sicker created LOG4J2-3354: --- Summary: Publish an SBOM with Log4j Key: LOG4J2-3354 URL: https://issues.apache.org/jira/browse/LOG4J2-3354 Project: Log4j 2 Issue Type: New Feature

[jira] [Comment Edited] (LOG4J2-3353) Additive property always set to true

[ https://issues.apache.org/jira/browse/LOG4J2-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479021#comment-17479021 ] Ralph Goers edited comment on LOG4J2-3353 at 1/19/22, 11:22 PM: The

[jira] [Resolved] (LOG4J2-3353) Additive property always set to true

[ https://issues.apache.org/jira/browse/LOG4J2-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3353. - Resolution: Information Provided > Additive property always set to true >

[jira] [Comment Edited] (LOG4J2-3353) Additive property always set to true

[ https://issues.apache.org/jira/browse/LOG4J2-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479021#comment-17479021 ] Ralph Goers edited comment on LOG4J2-3353 at 1/19/22, 11:21 PM: The

[GitHub] [logging-log4j2] carterkozak opened a new pull request #722: LOG4J2-3350: Evaluate configuration property substitutions eagerly

carterkozak opened a new pull request #722: URL: https://github.com/apache/logging-log4j2/pull/722 Previously lookups between configuration properties weren't evaluated until they were used in the configuration, which resulted in behavior more prohibitive for RoutingAppenders than

[jira] [Commented] (LOG4J2-3353) Additive property always set to true

[ https://issues.apache.org/jira/browse/LOG4J2-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479021#comment-17479021 ] Ralph Goers commented on LOG4J2-3353: - The additivity property is meaningless on the Root logger. 

[jira] [Comment Edited] (LOG4J2-3353) Additive property always set to true

[ https://issues.apache.org/jira/browse/LOG4J2-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479021#comment-17479021 ] Ralph Goers edited comment on LOG4J2-3353 at 1/19/22, 11:15 PM: The

[GitHub] [logging-log4j2] avandeursen commented on pull request #720: Expand test suite and fix NPE for StructuredDataLookup class

avandeursen commented on pull request #720: URL: https://github.com/apache/logging-log4j2/pull/720#issuecomment-1016886343 That did the trick. Thanks! -- 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

[GitHub] [logging-log4j2] carterkozak commented on pull request #720: Expand test suite and fix NPE for StructuredDataLookup class

carterkozak commented on pull request #720: URL: https://github.com/apache/logging-log4j2/pull/720#issuecomment-1016850499 I've retriggered the jobs :-) -- 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

[GitHub] [logging-log4j2] avandeursen commented on pull request #720: Expand test suite and fix NPE for StructuredDataLookup class

avandeursen commented on pull request #720: URL: https://github.com/apache/logging-log4j2/pull/720#issuecomment-1016848096 I doubt the failing build is related to the code change here. Is there an easier way to re-trigger the build than me pushing an empty commit? -- This is an

[jira] [Commented] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478940#comment-17478940 ] Ralph Goers commented on LOG4J2-3303: - That is a good question. From what I can tell Volkan

[CI][SUCCESS] Logging/log4j/release-2.x#769 back to normal

BUILD SUCCESS Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/769/ Project: release-2.x Date of build: Wed, 19 Jan 2022 17:34:54 + Build duration: 1 hr 7 min and counting JUnit Tests Name: (root) Failed: 0 test(s),

[jira] [Updated] (LOG4J2-3353) Additive property always set to true

[ https://issues.apache.org/jira/browse/LOG4J2-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitin Dominic updated LOG4J2-3353: -- Description: During upgrading log4j2 in grails 2.5.4 application, I removed all log4j 1.2.17

[jira] [Created] (LOG4J2-3353) Additive property always set to true

Jitin Dominic created LOG4J2-3353: - Summary: Additive property always set to true Key: LOG4J2-3353 URL: https://issues.apache.org/jira/browse/LOG4J2-3353 Project: Log4j 2 Issue Type: Bug

[CI][UNSTABLE] Logging/log4j/release-2.x#768 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/768/ Project: release-2.x Date of build: Wed, 19 Jan 2022 15:25:50 + Build duration: 1 hr 45 min and counting JUnit Tests Name: (root) Failed: 0 test(s),

[jira] [Commented] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478821#comment-17478821 ] Ramanan Ravi commented on LOG4J2-3303: -- [~vy] - thanks for your time and support on this. One quick

[jira] [Commented] (LOG4J2-3350) Routing appender does not expand nested variables

[ https://issues.apache.org/jira/browse/LOG4J2-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478816#comment-17478816 ] Gary D. Gregory commented on LOG4J2-3350: - Oops, I linked the wrong issue. > Routing appender

[jira] [Closed] (LOG4J2-3350) Routing appender does not expand nested variables

[ https://issues.apache.org/jira/browse/LOG4J2-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-3350. --- Fix Version/s: 2.17.2 Resolution: Fixed [~stemaio]  Please search Jira before

[GitHub] [logging-log4j2] avandeursen opened a new pull request #721: Expand test suite for DateLookup

avandeursen opened a new pull request #721: URL: https://github.com/apache/logging-log4j2/pull/721 This commit strengthens the test suite for the `DateLookup` class so that it achieves full branch coverage. The javadoc for the `lookup(event, key)` method incorrectly stated that the

[GitHub] [logging-log4j2] avandeursen opened a new pull request #720: Expand test suite and fix NPE for StructuredDataLookup class

avandeursen opened a new pull request #720: URL: https://github.com/apache/logging-log4j2/pull/720 This PR strengthens the test suite for the `StructuredDataLookup` class so that it achieves full branch coverage. The corner cases revealed the problem that a lookup of a null key with a

[GitHub] [logging-log4j2] ppkarwasz commented on a change in pull request #709: Adds default property values to TTCCLayout (Log4j 1.x bridge)

ppkarwasz commented on a change in pull request #709: URL: https://github.com/apache/logging-log4j2/pull/709#discussion_r787887554 ## File path: log4j-1.2-api/src/main/java/org/apache/log4j/builders/layout/TTCCLayoutBuilder.java ## @@ -91,10 +91,10 @@ public Layout

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #711: Use Log4j1XmlLayout instead of XmlLayout

ppkarwasz commented on pull request #711: URL: https://github.com/apache/logging-log4j2/pull/711#issuecomment-1016598479 @garydgregory: I cut the #706 commit into pieces and now every PR should have its own tests. -- This is an automated message from the Apache Git Service. To respond

[jira] [Commented] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478774#comment-17478774 ] Volkan Yazici commented on LOG4J2-3303: --- [~ramananravi], the changes are landed to both

[jira] [Resolved] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici resolved LOG4J2-3303. --- Resolution: Fixed > Add support for FileSize in TB > -- > >

[jira] [Updated] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici updated LOG4J2-3303: -- Fix Version/s: 2.17.2 > Add support for FileSize in TB > -- > >

[jira] [Commented] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478773#comment-17478773 ] ASF subversion and git services commented on LOG4J2-3303: - Commit

[GitHub] [logging-log4j2] vy closed pull request #671: [LOG4J2-3303] Add support for FileSize in TB

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

[GitHub] [logging-log4j2] vy commented on pull request #671: [LOG4J2-3303] Add support for FileSize in TB

vy commented on pull request #671: URL: https://github.com/apache/logging-log4j2/pull/671#issuecomment-1016578739 @ramananravi, it is on `release-2.x`. I will port this to `master`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[jira] [Commented] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478763#comment-17478763 ] ASF subversion and git services commented on LOG4J2-3303: - Commit

[jira] [Commented] (LOG4J2-3343) Add ability to use exclusion pattern filter on Map Resolver keys

[ https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478722#comment-17478722 ] Carter Kozak commented on LOG4J2-3343: -- I agree with Volkan here, I have a strong preference for

[jira] [Updated] (LOG4J2-3347) Test failure in TypeConverterRegistryTest (master only)

[ https://issues.apache.org/jira/browse/LOG4J2-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3347: Affects Version/s: 3.0.0 > Test failure in TypeConverterRegistryTest (master only) >

[jira] [Commented] (LOG4J2-3347) Test failure in TypeConverterRegistryTest (master only)

[ https://issues.apache.org/jira/browse/LOG4J2-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478687#comment-17478687 ] Gary D. Gregory commented on LOG4J2-3347: - [~mattsicker] If you use the ticket number in the

[GitHub] [logging-log4j2] vy merged pull request #719: Bump maven-source-plugin from 3.0.1 to 3.2.1

vy merged pull request #719: URL: https://github.com/apache/logging-log4j2/pull/719 -- 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:

[GitHub] [logging-log4j-scala] vy merged pull request #16: ci: Scala 2.13.8

vy merged pull request #16: URL: https://github.com/apache/logging-log4j-scala/pull/16 -- 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:

[jira] [Work started] (LOG4J2-3303) Add support for FileSize in TB

[ https://issues.apache.org/jira/browse/LOG4J2-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3303 started by Volkan Yazici. - > Add support for FileSize in TB > -- > >

[jira] [Reopened] (LOG4J2-3238) Log4j 1.2 bridge API doesn't write the messages to rsyslog in proper "PatternLayout" mentioned in log4j.properties file when SysLogAppender is used

[ https://issues.apache.org/jira/browse/LOG4J2-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tukesh reopened LOG4J2-3238: {{I think "org.apache.log4j.net.SyslogAppender" }}should  work with bridge API when compatibility flag is

[jira] [Created] (LOG4J2-3352) Log4j 1.2 bridge API hard codes the Syslog Host and port to locathost:514

Tukesh created LOG4J2-3352: -- Summary: Log4j 1.2 bridge API hard codes the Syslog Host and port to locathost:514 Key: LOG4J2-3352 URL: https://issues.apache.org/jira/browse/LOG4J2-3352 Project: Log4j 2

[jira] [Updated] (LOG4J2-3352) Log4j 1.2 bridge API hard codes the Syslog Host and port to localhost:514

[ https://issues.apache.org/jira/browse/LOG4J2-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tukesh updated LOG4J2-3352: --- Summary: Log4j 1.2 bridge API hard codes the Syslog Host and port to localhost:514 (was: Log4j 1.2 bridge

[jira] [Created] (LOG4J2-3351) JDBC Appender not working for consecutive log events with OracleDB

Rudranshu created LOG4J2-3351: - Summary: JDBC Appender not working for consecutive log events with OracleDB Key: LOG4J2-3351 URL: https://issues.apache.org/jira/browse/LOG4J2-3351 Project: Log4j 2

[jira] [Commented] (LOG4J2-3343) Add ability to use exclusion pattern filter on Map Resolver keys

[ https://issues.apache.org/jira/browse/LOG4J2-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17478632#comment-17478632 ] Volkan Yazici commented on LOG4J2-3343: --- There are many features we can support in the filtering

[jira] [Updated] (LOG4J2-3339) FilePattern doesn't rotate correctly when not using a Filename

[ https://issues.apache.org/jira/browse/LOG4J2-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miguel Valente updated LOG4J2-3339: --- Priority: Major (was: Minor) > FilePattern doesn't rotate correctly when not using a

[jira] [Created] (LOG4J2-3350) Routing appender does not expand nested variables

Stefano Maioli created LOG4J2-3350: -- Summary: Routing appender does not expand nested variables Key: LOG4J2-3350 URL: https://issues.apache.org/jira/browse/LOG4J2-3350 Project: Log4j 2

[jira] [Created] (LOG4J2-3349) RollingFileAppenderBuilder in log4j1 bridge does not create the appender as in log4j1

Achim created LOG4J2-3349: - Summary: RollingFileAppenderBuilder in log4j1 bridge does not create the appender as in log4j1 Key: LOG4J2-3349 URL: https://issues.apache.org/jira/browse/LOG4J2-3349 Project: