[jira] [Comment Edited] (LOG4J2-3356) The sub module log4j-layout-template-json seems not properly configured to be deployed as a fragment host in OSGI

[ https://issues.apache.org/jira/browse/LOG4J2-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485553#comment-17485553 ] Ralph Goers edited comment on LOG4J2-3356 at 2/2/22, 2:56 AM: -- Looking at

[jira] [Commented] (LOG4J2-3356) The sub module log4j-layout-template-json seems not properly configured to be deployed as a fragment host in OSGI

[ https://issues.apache.org/jira/browse/LOG4J2-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485553#comment-17485553 ] Ralph Goers commented on LOG4J2-3356: - Looking at

[jira] [Updated] (LOG4J2-3356) The sub module log4j-layout-template-json seems not properly configured to be deployed as a fragment host in OSGI

[ https://issues.apache.org/jira/browse/LOG4J2-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-3356: Attachment: image-2022-02-01-19-53-38-377.png > The sub module log4j-layout-template-json seems

[jira] [Commented] (LOG4J2-3356) The sub module log4j-layout-template-json seems not properly configured to be deployed as a fragment host in OSGI

[ https://issues.apache.org/jira/browse/LOG4J2-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485511#comment-17485511 ] ruffp commented on LOG4J2-3356: --- from here:

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485494#comment-17485494 ] leor amikam commented on LOG4J2-3383: - [~rgoers]  Thanks for the response!  Will look into that. >

[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=17485453#comment-17485453 ] Ralph Goers commented on LOG4J2-3303: - I have confirmed it. The fix should be good. > Add support

[jira] [Updated] (LOG4NET-685) Broken XmlLayoutSchemaLog4j

[ https://issues.apache.org/jira/browse/LOG4NET-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Stiller updated LOG4NET-685: --- Description: After updating from version 2.0.8 to 2.0.14, using XmlLayoutSchemaLog4j seems

[jira] [Commented] (LOG4J2-3381) Programmatically configuring Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485420#comment-17485420 ] Ralph Goers commented on LOG4J2-3381: - Once you have called context.setConfiguration() you should

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

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory edited comment on LOG4J2-3351 at 2/1/22, 7:04 PM: --

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

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory edited comment on LOG4J2-3351 at 2/1/22, 7:04 PM: --

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

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory edited comment on LOG4J2-3351 at 2/1/22, 7:03 PM: --

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

[ https://issues.apache.org/jira/browse/LOG4J2-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485417#comment-17485417 ] Gary D. Gregory commented on LOG4J2-3351: - Please run your use case with DEBUG on for Log4j

[jira] [Resolved] (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 ] Gary D. Gregory resolved LOG4J2-3352. - Resolution: Information Provided > Log4j 1.2 bridge API hard codes the Syslog Host and

[jira] [Comment Edited] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485415#comment-17485415 ] Ralph Goers edited comment on LOG4J2-3383 at 2/1/22, 6:45 PM: --

[jira] [Comment Edited] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485415#comment-17485415 ] Ralph Goers edited comment on LOG4J2-3383 at 2/1/22, 6:44 PM: --

[jira] [Comment Edited] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485415#comment-17485415 ] Ralph Goers edited comment on LOG4J2-3383 at 2/1/22, 6:42 PM: --

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485415#comment-17485415 ] Ralph Goers commented on LOG4J2-3383: - CVE-2017-5645 started our hunt for

[jira] [Commented] (LOG4J2-3380) Log4j syslog appender misses writing the 1st event after syslog service is restarted

[ https://issues.apache.org/jira/browse/LOG4J2-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485375#comment-17485375 ] Loganathan commented on LOG4J2-3380: Thanks again [~rgoers]. We will work on this and will get back

[jira] [Comment Edited] (LOG4J2-3380) Log4j syslog appender misses writing the 1st event after syslog service is restarted

[ https://issues.apache.org/jira/browse/LOG4J2-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485368#comment-17485368 ] Ralph Goers edited comment on LOG4J2-3380 at 2/1/22, 4:56 PM: -- I believe

[jira] [Commented] (LOG4J2-3380) Log4j syslog appender misses writing the 1st event after syslog service is restarted

[ https://issues.apache.org/jira/browse/LOG4J2-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485368#comment-17485368 ] Ralph Goers commented on LOG4J2-3380: - I believe that is pretty much what I said. The OS doesn't

[jira] [Commented] (LOG4J2-3366) Fix order of property sources

[ https://issues.apache.org/jira/browse/LOG4J2-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485364#comment-17485364 ] Ralph Goers commented on LOG4J2-3366: - I agree with this change. However, I do want to point out

[jira] [Commented] (LOG4J2-3380) Log4j syslog appender misses writing the 1st event after syslog service is restarted

[ https://issues.apache.org/jira/browse/LOG4J2-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485356#comment-17485356 ] Loganathan commented on LOG4J2-3380: Thanks, [~rgoers] We didn't observe the last message being lost

[GitHub] [logging-log4j2] carterkozak commented on pull request #735: Adds a shorthand method to specify components names

carterkozak commented on pull request #735: URL: https://github.com/apache/logging-log4j2/pull/735#issuecomment-1027030918 It sounds like we're discussing improving several different parts of the properties configuration scheme at once -- It's great to have an idea of where we want to go

[jira] [Comment Edited] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484742#comment-17484742 ] Gary D. Gregory edited comment on LOG4J2-3372 at 2/1/22, 4:23 PM: -- It

[jira] [Updated] (LOG4NET-685) Broken XmlLayoutSchemaLog4j

[ https://issues.apache.org/jira/browse/LOG4NET-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Stiller updated LOG4NET-685: --- Environment: Windows 11 Professional, Windows 10 Professional, Windows Server 2012 R2,

[jira] [Commented] (LOG4J2-3382) ${ctx:mdcValue} no longer populating in Property tag

[ https://issues.apache.org/jira/browse/LOG4J2-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485333#comment-17485333 ] Carter Kozak commented on LOG4J2-3382: -- This PR addresses the ability to use properties within a

[jira] [Comment Edited] (LOG4J2-3372) ConsoleAppender on Windows does not use platform default encoding

[ https://issues.apache.org/jira/browse/LOG4J2-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484742#comment-17484742 ] Gary D. Gregory edited comment on LOG4J2-3372 at 2/1/22, 3:34 PM: -- It

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485282#comment-17485282 ] leor amikam commented on LOG4J2-3383: - [~rgoers]  do you recall which CVE required the change? >

[jira] [Comment Edited] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485275#comment-17485275 ] leor amikam edited comment on LOG4J2-3383 at 2/1/22, 2:25 PM: -- [~rgoers] is

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485275#comment-17485275 ] leor amikam commented on LOG4J2-3383: - [~rgoers] is there any doc on how to hook in a 

[jira] [Comment Edited] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485275#comment-17485275 ] leor amikam edited comment on LOG4J2-3383 at 2/1/22, 2:24 PM: -- [~rgoers] is

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485272#comment-17485272 ] leor amikam commented on LOG4J2-3383: - [~rgoers] Yes, I am pretty sire it it.  I will take a look at

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485271#comment-17485271 ] Ralph Goers commented on LOG4J2-3383: - Are you sending the messages using the SerializedLayout? I

[jira] [Comment Edited] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

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

[jira] [Commented] (LOG4NET-685) Broken XmlLayoutSchemaLog4j

[ https://issues.apache.org/jira/browse/LOG4NET-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485261#comment-17485261 ] Maciej Stiller commented on LOG4NET-685: * Downgrading to 2.0.13 yielded same results *

[jira] [Updated] (LOG4NET-685) Broken XmlLayoutSchemaLog4j

[ https://issues.apache.org/jira/browse/LOG4NET-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Stiller updated LOG4NET-685: --- Summary: Broken XmlLayoutSchemaLog4j (was: Broken XmlLayoutSchemaLog4j in ) > Broken

[jira] [Commented] (LOG4J2-3383) JMS Log deserialization is failing on jboss eap after upgrade to 2.17.1

[ https://issues.apache.org/jira/browse/LOG4J2-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485260#comment-17485260 ] Gary D. Gregory commented on LOG4J2-3383: - Hello [~leor.ami...@hsntech.com] I do not see

[jira] [Created] (LOG4NET-685) Broken XmlLayoutSchemaLog4j in

Maciej Stiller created LOG4NET-685: -- Summary: Broken XmlLayoutSchemaLog4j in Key: LOG4NET-685 URL: https://issues.apache.org/jira/browse/LOG4NET-685 Project: Log4net Issue Type: Bug

[jira] [Commented] (LOG4J2-3366) Fix order of property sources

[ https://issues.apache.org/jira/browse/LOG4J2-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485220#comment-17485220 ] Volkan Yazici commented on LOG4J2-3366: --- I agree that * current ordering is broken (granted it