[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370276#comment-15370276 ] Luigi Alice commented on LOG4J2-875: Hi, Problem still exists in Log4j2 version 2.5

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370279#comment-15370279 ] Remko Popma commented on LOG4J2-1182: - [~mallox] Is this still a problem? Note that t

[jira] [Closed] (LOG4J2-772) Performance enhancement: ParameterizedMessage should not take String snapshots of its parameters in constructor

[ https://issues.apache.org/jira/browse/LOG4J2-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-772. -- Resolution: Resolved Assignee: Remko Popma Fix Version/s: 2.6 ParameterizedMessage has b

[jira] [Updated] (LOG4J2-1199) Document that JVM Input Arguments Lookup (JMX) is not available on Google App Engine. (was: "log4j2.disable.jmx" property is not aware of class JmxRuntimeInputArgumentsL

[ https://issues.apache.org/jira/browse/LOG4J2-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1199: Fix Version/s: 2.7 Component/s: Documentation Issue Type: Documentation (was: Bug)

[jira] [Commented] (LOG4J2-1059) log4j2 Configuration File not found in shaded jar

[ https://issues.apache.org/jira/browse/LOG4J2-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370315#comment-15370315 ] Remko Popma commented on LOG4J2-1059: - Should we document Günther's solution for this

[jira] [Commented] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned

[ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370316#comment-15370316 ] piero de salvia commented on LOG4J2-1379: - Sure: pom.xml:

[jira] [Commented] (LOG4J2-1279) NullPointerException in FastDateParser$TimeZoneStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370318#comment-15370318 ] Remko Popma commented on LOG4J2-1279: - Added link to LOG4J2-1102 (although not sure h

[jira] [Updated] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned

[ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] piero de salvia updated LOG4J2-1379: Attachment: log4j2.yaml log4j2.xml > Documentation is subzero quality as fa

[jira] [Updated] (LOG4J2-1313) not working

[ https://issues.apache.org/jira/browse/LOG4J2-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1313: Fix Version/s: 2.7 > not working > - > > K

[jira] [Commented] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned

[ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370325#comment-15370325 ] Remko Popma commented on LOG4J2-1379: - [~piero] Tip: you can preserve whitespace in J

[jira] [Comment Edited] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370276#comment-15370276 ] Remko Popma edited comment on LOG4J2-875 at 7/11/16 7:51 AM: -

[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370344#comment-15370344 ] Remko Popma commented on LOG4J2-875: [~Luigi] Thanks for the quick response! I still

[jira] [Commented] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned

[ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370359#comment-15370359 ] piero de salvia commented on LOG4J2-1379: - {code}

[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370401#comment-15370401 ] Luigi Alice commented on LOG4J2-875: Hello, It does not rollover at all. But the Log

[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370427#comment-15370427 ] Remko Popma commented on LOG4J2-875: Luigi, thanks for that information. If you set

[jira] [Commented] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned

[ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370441#comment-15370441 ] Remko Popma commented on LOG4J2-1379: - Good stuff, thanks! Quick comments: * status

[jira] [Comment Edited] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned

[ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370316#comment-15370316 ] Remko Popma edited comment on LOG4J2-1379 at 7/11/16 9:29 AM: -

[jira] [Commented] (LOG4J2-1350) Circuit Breaker for log system to avoid DOS by recursion

[ https://issues.apache.org/jira/browse/LOG4J2-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370473#comment-15370473 ] Steffen Offermann commented on LOG4J2-1350: --- @[~rem...@yahoo.com]: Thanks for y

[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370489#comment-15370489 ] Luigi Alice commented on LOG4J2-875: Hm, it's a strange behavior. It's not completely

[jira] [Closed] (LOG4J2-1350) Circuit Breaker for log system to avoid DOS by recursion

[ https://issues.apache.org/jira/browse/LOG4J2-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1350. --- Resolution: Fixed Fix Version/s: 2.6 Great. Closing this issue as Fixed. Please feel free to r

[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370564#comment-15370564 ] Remko Popma commented on LOG4J2-875: Is it possible that during the first rollover at

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370586#comment-15370586 ] Joern Huxhorn commented on LOG4J2-1226: --- I certainly have other formats for receivi

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370656#comment-15370656 ] Ralph Goers commented on LOG4J2-1226: - 1. I understand the arguments you are making (

[jira] [Comment Edited] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370656#comment-15370656 ] Ralph Goers edited comment on LOG4J2-1226 at 7/11/16 12:42 PM:

[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370727#comment-15370727 ] Luigi Alice commented on LOG4J2-875: Ok. The current situation is no problem for us. A

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370756#comment-15370756 ] Joern Huxhorn commented on LOG4J2-1226: --- We don't need to discuss the pros and cons

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371040#comment-15371040 ] Leon Finker commented on LOG4J2-1457: - Proposing only the following changes. Basicall

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371261#comment-15371261 ] Gary Gregory commented on LOG4J2-1457: -- Hi [~leonfin], Can you provide a patch file

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371375#comment-15371375 ] Matt Sicker commented on LOG4J2-1457: - Doesn't Loader.loadClass() do the same thing a

[jira] [Commented] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned

[ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371414#comment-15371414 ] Matt Sicker commented on LOG4J2-1379: - One thing that would help would be more exampl

[jira] [Commented] (LOG4J2-1059) log4j2 Configuration File not found in shaded jar

[ https://issues.apache.org/jira/browse/LOG4J2-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371421#comment-15371421 ] Matt Sicker commented on LOG4J2-1059: - That sounds like a good idea. Ideally, we shou

[jira] [Commented] (LOG4J2-1059) log4j2 Configuration File not found in shaded jar

[ https://issues.apache.org/jira/browse/LOG4J2-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371423#comment-15371423 ] Ralph Goers commented on LOG4J2-1059: - We really should have a tool that does it. >

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371462#comment-15371462 ] Ravi Gairola commented on LOG4J2-1182: -- Sorry, but I no longer have access to that c

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371540#comment-15371540 ] Leon Finker commented on LOG4J2-1457: - Loader.loadClass() could call Class.forName(cl

[jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker updated LOG4J2-1457: Attachment: LOG4J2-1457.patch Hi Gary, please review LOG4J2-1457.patch Thank you > Class loader de

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371766#comment-15371766 ] Matt Sicker commented on LOG4J2-1457: - I think it would make more sense to make a sep

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371899#comment-15371899 ] Ralph Goers commented on LOG4J2-1457: - The patch looks fine to me. I don't think a se

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371962#comment-15371962 ] Matt Sicker commented on LOG4J2-1457: - Now that I look more closely, the only place c

[jira] [Created] (LOG4J2-1460) Multiple structured data elements in syslog while using combination of StructuredDataMessage and MDC

Priya Ahuja created LOG4J2-1460: --- Summary: Multiple structured data elements in syslog while using combination of StructuredDataMessage and MDC Key: LOG4J2-1460 URL: https://issues.apache.org/jira/browse/LOG4J2-1460

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372003#comment-15372003 ] Remko Popma commented on LOG4J2-1457: - Very nice detective work on the deadlock, Leon

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372064#comment-15372064 ] Leon Finker commented on LOG4J2-1457: - Yes that's what I tried at first. But then thi

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372135#comment-15372135 ] Matt Sicker commented on LOG4J2-1457: - I don't think that unit test is correct. The