[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974936#comment-15974936 ] Ralph Goers commented on LOG4J2-1883: - I am about to introduce a commit that requires everything to

[jira] [Commented] (LOG4J2-1359) Add support for Java 9 StackWalker API in ReflectionUtil

[ https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978166#comment-15978166 ] Ralph Goers commented on LOG4J2-1359: - This has now been pushed to master. > Add support for Java 9

[jira] [Comment Edited] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968275#comment-15968275 ] Ralph Goers edited comment on LOG4J2-1883 at 4/13/17 9:54 PM: -- No, none of

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969251#comment-15969251 ] Ralph Goers commented on LOG4J2-1883: - The current limitations are that the only real time clock

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107669#comment-16107669 ] Ralph Goers commented on LOG4J2-1990: - I have a use case with Audit logging where I only want a

[jira] [Issue Comment Deleted] (LOG4J2-1311) SocketAppender will lose several events after re-connection to server

[ https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1311: Comment: was deleted (was: Hi, I am not feeling well and will be on sick leave. Please reach out

[jira] [Created] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

Ralph Goers created LOG4J2-2008: --- Summary: RFC5424Layout should support multiple StructuredData elements. Key: LOG4J2-2008 URL: https://issues.apache.org/jira/browse/LOG4J2-2008 Project: Log4j 2

[jira] [Commented] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125260#comment-16125260 ] Ralph Goers commented on LOG4J2-1964: - See LOG4J2-2009. The test above is invalid. > Dynamic

[jira] [Resolved] (LOG4J2-2009) Rolling appender managers broken on pattern/policy reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2009. - Resolution: Invalid Actually, the stack trace above proves the LOG4J2-1964 is fixed. You are

[jira] [Resolved] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

[ https://issues.apache.org/jira/browse/LOG4J2-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2019. - Resolution: Invalid Fix Version/s: (was: 2.8.2) If you are running on a Unix-based

[jira] [Closed] (LOG4J2-2019) Where does the LogEvents go when the active log file is deleted?

[ https://issues.apache.org/jira/browse/LOG4J2-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2019. --- > Where does the LogEvents go when the active log file is deleted? >

[jira] [Commented] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089748#comment-16089748 ] Ralph Goers commented on LOG4J2-1980: - If it is a system property it should be specified as

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078794#comment-16078794 ] Ralph Goers commented on LOG4J2-1933: - Although json.org says an object is an unordered set of

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078961#comment-16078961 ] Ralph Goers commented on LOG4J2-1883: - I looked at the code and it seems to require Java 8. Frankly,

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085142#comment-16085142 ] Ralph Goers edited comment on LOG4J2-1971 at 7/13/17 4:17 AM: -- So the

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085112#comment-16085112 ] Ralph Goers edited comment on LOG4J2-1971 at 7/13/17 3:30 AM: -- I see a few

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085112#comment-16085112 ] Ralph Goers commented on LOG4J2-1971: - I see a few classes missing from the

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085142#comment-16085142 ] Ralph Goers commented on LOG4J2-1971: - So the difference between 2.8.2 and 2.9 is that in 2.9

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085142#comment-16085142 ] Ralph Goers edited comment on LOG4J2-1971 at 7/13/17 3:47 AM: -- So the

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085065#comment-16085065 ] Ralph Goers commented on LOG4J2-1971: - Why is pax logging in the picture? The Activator class is in

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085194#comment-16085194 ] Ralph Goers commented on LOG4J2-1971: - It should be the correct class loader. It is the ClassLoader

[jira] [Commented] (LOG4J2-1979) Refactoring of StrSubstitutor

[ https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088620#comment-16088620 ] Ralph Goers commented on LOG4J2-1979: - I thought it already does. > Refactoring of StrSubstitutor >

[jira] [Commented] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091143#comment-16091143 ] Ralph Goers commented on LOG4J2-1980: - That would mean that weblogic.Name is not actually a system

[jira] [Comment Edited] (LOG4J2-1980) log4j2.properties substitution ${} ie.${weblogic.Name} not working in WebLogic 12.1.3

[ https://issues.apache.org/jira/browse/LOG4J2-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091143#comment-16091143 ] Ralph Goers edited comment on LOG4J2-1980 at 7/18/17 5:53 AM: -- That would

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089171#comment-16089171 ] Ralph Goers edited comment on LOG4J2-1971 at 7/16/17 10:51 PM: --- Well, it

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089171#comment-16089171 ] Ralph Goers edited comment on LOG4J2-1971 at 7/16/17 10:51 PM: --- Well, it

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089201#comment-16089201 ] Ralph Goers commented on LOG4J2-1971: - You are absolutely correct. Adding the file url I get {code}

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089171#comment-16089171 ] Ralph Goers commented on LOG4J2-1971: - Well, it worked for me yesterday. Today I get karaf@root()>

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089171#comment-16089171 ] Ralph Goers edited comment on LOG4J2-1971 at 7/16/17 10:50 PM: --- Well, it

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088650#comment-16088650 ] Ralph Goers edited comment on LOG4J2-1971 at 7/15/17 4:25 PM: -- Well, thats

[jira] [Reopened] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-1971: - Reopening the issue. Just to mark it resolved again. Please verify the fix. > ClassCastException:

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094625#comment-16094625 ] Ralph Goers commented on LOG4J2-1921: - You should not have needed Log4J-core. > Getting

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092605#comment-16092605 ] Ralph Goers commented on LOG4J2-1921: - I created a branch named "android" which has a

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091963#comment-16091963 ] Ralph Goers commented on LOG4J2-1883: - If we wanted to go the the trouble to create our own Instant

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092682#comment-16092682 ] Ralph Goers commented on LOG4J2-1921: - Gradie? We use Maven as our build tool and git for source

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096526#comment-16096526 ] Ralph Goers commented on LOG4J2-1921: - Although I'm not sure when I will have the time I'd love the

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096193#comment-16096193 ] Ralph Goers edited comment on LOG4J2-1921 at 7/21/17 12:46 PM: --- Above you

[jira] [Commented] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096851#comment-16096851 ] Ralph Goers commented on LOG4J2-1984: - No. There has always been a max. It was 32 (and still is by

[jira] [Closed] (LOG4J2-1984) Allow max length of StructuredDataMessage keys to be user defined

[ https://issues.apache.org/jira/browse/LOG4J2-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1984. --- > Allow max length of StructuredDataMessage keys to be user defined >

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102862#comment-16102862 ] Ralph Goers commented on LOG4J2-1990: - https://logging.apache.org/log4j/2.x/manual/async.html already

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102940#comment-16102940 ] Ralph Goers commented on LOG4J2-1990: - The bottom line is that when this happens it is user error. We

[jira] [Closed] (LOG4J2-1992) RollingFileAppender violate maxfilesize limit.

[ https://issues.apache.org/jira/browse/LOG4J2-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1992. --- Resolution: Invalid I am sorry, but Jira is for Log4j 2 problems only. Furthermore, none of the

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104179#comment-16104179 ] Ralph Goers commented on LOG4J2-1990: - In my opinion Log4J should never be the cause of an

[jira] [Commented] (LOG4J2-1988) java.util.ConcurrentModificationException with AsyncLogger?

[ https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104216#comment-16104216 ] Ralph Goers commented on LOG4J2-1988: - The AppenderControl should be catching these and then only

[jira] [Comment Edited] (LOG4J2-1988) java.util.ConcurrentModificationException with AsyncLogger?

[ https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104216#comment-16104216 ] Ralph Goers edited comment on LOG4J2-1988 at 7/28/17 12:46 AM: --- The

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103701#comment-16103701 ] Ralph Goers commented on LOG4J2-1990: - yeah, that looks ok. > ConcurrentModificationException

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104461#comment-16104461 ] Ralph Goers commented on LOG4J2-1990: - Yes, it should catch Exception. >

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096193#comment-16096193 ] Ralph Goers edited comment on LOG4J2-1921 at 7/21/17 12:44 PM: --- Above you

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096193#comment-16096193 ] Ralph Goers commented on LOG4J2-1921: - Above you mention you use xml configuration but I don't see

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096364#comment-16096364 ] Ralph Goers commented on LOG4J2-1921: - OK. The Logcat appender does essentially what

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068785#comment-16068785 ] Ralph Goers commented on LOG4J2-1934: - As I suggested before, take a look at how the TCP Socket

[jira] [Comment Edited] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068545#comment-16068545 ] Ralph Goers edited comment on LOG4J2-1934 at 6/29/17 4:16 PM: -- I just took a

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16068545#comment-16068545 ] Ralph Goers commented on LOG4J2-1934: - I just took a look at the commit and I do NOT like this

[jira] [Updated] (LOG4J2-1311) SocketAppender will lose several events after re-connection to server

[ https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1311: Description: ---> Firstly, I'd like to describe some conditions of our environment: 1) Our

[jira] [Updated] (LOG4J2-1311) SocketAppender will lose several events after re-connection to server

[ https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1311: Summary: SocketAppender will lose several events after re-connection to server (was:

[jira] [Commented] (LOG4J2-1990) ConcurrentModificationException logging a parameter of type Map

[ https://issues.apache.org/jira/browse/LOG4J2-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104432#comment-16104432 ] Ralph Goers commented on LOG4J2-1990: - Remko, my position is that if an application callers a logger

[jira] [Commented] (LOG4J2-2002) DefaultConfigurationBuilder.writeXmlAttributes does not handle null attribute values

[ https://issues.apache.org/jira/browse/LOG4J2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129358#comment-16129358 ] Ralph Goers commented on LOG4J2-2002: - I'd have to check the code. Event if ConfigurationBuilder does

[jira] [Commented] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137094#comment-16137094 ] Ralph Goers commented on LOG4J2-1925: - I have submitted a bug report with Oracle. Waiting for a

[jira] [Resolved] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1925. - Resolution: Fixed I have created a test project at https://github.com/rgoers/LOG4J2-1925 without

[jira] [Comment Edited] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134684#comment-16134684 ] Ralph Goers edited comment on LOG4J2-1086 at 8/21/17 4:05 AM: -- Perrick, The

[jira] [Commented] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134684#comment-16134684 ] Ralph Goers commented on LOG4J2-1086: - Perrick, The creates 100 Excectuors on 32 threads. Each of

[jira] [Resolved] (LOG4J2-2022) RFC5424Layout should obtain the process id.

[ https://issues.apache.org/jira/browse/LOG4J2-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2022. - Resolution: Fixed > RFC5424Layout should obtain the process id. >

[jira] [Closed] (LOG4J2-2022) RFC5424Layout should obtain the process id.

[ https://issues.apache.org/jira/browse/LOG4J2-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2022. --- > RFC5424Layout should obtain the process id. > --- > >

[jira] [Created] (LOG4J2-2022) RFC5424Layout should obtain the process id.

Ralph Goers created LOG4J2-2022: --- Summary: RFC5424Layout should obtain the process id. Key: LOG4J2-2022 URL: https://issues.apache.org/jira/browse/LOG4J2-2022 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-2013) SslSocketManager does not apply SSLContext on TCP reconnect

[ https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137356#comment-16137356 ] Ralph Goers commented on LOG4J2-2013: - Can you elaborate on the compatibility problem? We would

[jira] [Commented] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137862#comment-16137862 ] Ralph Goers commented on LOG4J2-1925: - The first time I ran the test with my Processor class it

[jira] [Resolved] (LOG4J2-1833) NullPointerException using fileName property of RollingFile Appender with DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1833. - Resolution: Fixed Fix Version/s: 2.9 The fix has been applied. Please verify and close.

[jira] [Comment Edited] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137094#comment-16137094 ] Ralph Goers edited comment on LOG4J2-1925 at 8/23/17 1:58 PM: -- I have

[jira] [Resolved] (LOG4J2-2024) TimeBasedTriggeringPolicy not work if no log written in the next hour

[ https://issues.apache.org/jira/browse/LOG4J2-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2024. - Resolution: Not A Bug By design, TimeBasedTriggeringPolicy only determines if it is time to roll

[jira] [Commented] (LOG4J2-1866) Add default value to MdcPatternConverter

[ https://issues.apache.org/jira/browse/LOG4J2-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009972#comment-16009972 ] Ralph Goers commented on LOG4J2-1866: - I dislike {{key=default}}. It looks like an assignment. I

[jira] [Updated] (LOG4J2-1904) facility setted to syslogappendar don't work,but user facility is being used.

[ https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1904: Description: Hello The following is my settings. {code} {code} But the facility

[jira] [Updated] (LOG4J2-1904) facility setted to syslogappendar don't work,but user facility is being used.

[ https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1904: Description: Hello The following is my settings. {code} {code} But the facility

[jira] [Resolved] (LOG4J2-1904) facility setted to syslogappendar don't work,but user facility is being used.

[ https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1904. - Resolution: Not A Problem The default layout(s) for the syslog appender are the SyslogLayout and

[jira] [Comment Edited] (LOG4J2-1904) facility setted to syslogappendar don't work,but user facility is being used.

[ https://issues.apache.org/jira/browse/LOG4J2-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005836#comment-16005836 ] Ralph Goers edited comment on LOG4J2-1904 at 5/11/17 3:36 AM: -- The default

[jira] [Assigned] (LOG4J2-1928) RollingRandomAccessFileAppender with DirectWriteRolloverStrategy requires a fileName

[ https://issues.apache.org/jira/browse/LOG4J2-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1928: --- Assignee: Ralph Goers > RollingRandomAccessFileAppender with DirectWriteRolloverStrategy

[jira] [Commented] (LOG4J2-1894) Potential data race in ReconfigurationDeadlockTest

[ https://issues.apache.org/jira/browse/LOG4J2-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042293#comment-16042293 ] Ralph Goers commented on LOG4J2-1894: - There is a race here but it is accounted for by the loop.

[jira] [Assigned] (LOG4J2-1894) Potential data race in ReconfigurationDeadlockTest

[ https://issues.apache.org/jira/browse/LOG4J2-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1894: --- Assignee: Ralph Goers > Potential data race in ReconfigurationDeadlockTest >

[jira] [Assigned] (LOG4J2-1916) Nullpointer with DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1916: --- Assignee: Ralph Goers > Nullpointer with DirectWriteRolloverStrategy >

[jira] [Assigned] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1925: --- Assignee: Ralph Goers > Having log4j-core on the compile classpath somehow breaks

[jira] [Assigned] (LOG4J2-1794) Programmatic reconfiguration doesn't affect existing loggers

[ https://issues.apache.org/jira/browse/LOG4J2-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1794: --- Assignee: Ralph Goers > Programmatic reconfiguration doesn't affect existing loggers >

[jira] [Commented] (LOG4J2-1793) Why there can't get thrown from LogEvent

[ https://issues.apache.org/jira/browse/LOG4J2-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042297#comment-16042297 ] Ralph Goers commented on LOG4J2-1793: - Is there anything to do on this or can it be closed? > Why

[jira] [Commented] (LOG4J2-1746) Add JDK9 build to Jenkins

[ https://issues.apache.org/jira/browse/LOG4J2-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042299#comment-16042299 ] Ralph Goers commented on LOG4J2-1746: - I don't think we need this any more. > Add JDK9 build to

[jira] [Commented] (LOG4J2-1745) Add support for multi-release jars for JDK9+

[ https://issues.apache.org/jira/browse/LOG4J2-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042300#comment-16042300 ] Ralph Goers commented on LOG4J2-1745: - I tried using multi-release jars and ran into trouble with

[jira] [Assigned] (LOG4J2-1798) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1798: --- Assignee: Ralph Goers > InterruptedException on RollingFileManager#rollover() >

[jira] [Assigned] (LOG4J2-1686) Support conditional configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1686: --- Assignee: Ralph Goers > Support conditional configuration >

[jira] [Updated] (LOG4J2-1686) Add support for properties selectors

[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1686: Summary: Add support for properties selectors (was: Support conditional configuration) > Add

[jira] [Commented] (LOG4J2-1729) CronTriggeringPolicy using "evaluateOnStartup" cause dead lock

[ https://issues.apache.org/jira/browse/LOG4J2-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042285#comment-16042285 ] Ralph Goers commented on LOG4J2-1729: - Can you validate that this still happens with 2.8.2.

[jira] [Assigned] (LOG4J2-1828) add support for prudent mode in Log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1828: --- Assignee: Ralph Goers > add support for prudent mode in Log4j 2 >

[jira] [Commented] (LOG4J2-1727) Calling static method during re-/undeploy causes memory leak in Tomcat

[ https://issues.apache.org/jira/browse/LOG4J2-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042302#comment-16042302 ] Ralph Goers commented on LOG4J2-1727: - Log4j documents that it must be shutdown last for this exact

[jira] [Commented] (LOG4J2-1675) Compile-time incompatibility regarding SimpleMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042303#comment-16042303 ] Ralph Goers commented on LOG4J2-1675: - Are we going to do anything with this or should it just be

[jira] [Comment Edited] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056655#comment-16056655 ] Ralph Goers edited comment on LOG4J2-1699 at 6/20/17 11:22 PM: --- The Jenkins

[jira] [Reopened] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-1699: - The Jenkins build now has a unit test failing. org.junit.ComparisonFailure: expected:

[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057548#comment-16057548 ] Ralph Goers commented on LOG4J2-1699: - I haven't looked at the patch but I just wanted to say that we

[jira] [Commented] (LOG4J2-1946) DefaultRolloverStrategy is failing if some log file is deleted from the current sequence

[ https://issues.apache.org/jira/browse/LOG4J2-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054376#comment-16054376 ] Ralph Goers commented on LOG4J2-1946: - OK. Looking at the code I can see that the file renaming will

[jira] [Comment Edited] (LOG4J2-1946) DefaultRolloverStrategy is failing if some log file is deleted from the current sequence

[ https://issues.apache.org/jira/browse/LOG4J2-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054297#comment-16054297 ] Ralph Goers edited comment on LOG4J2-1946 at 6/19/17 4:42 PM: -- I guess this

[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061827#comment-16061827 ] Ralph Goers commented on LOG4J2-1699: - For item 2, If there is an error configuring an element

[jira] [Commented] (LOG4J2-1946) DefaultRolloverStrategy is failing if some log file is deleted from the current sequence

[ https://issues.apache.org/jira/browse/LOG4J2-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054297#comment-16054297 ] Ralph Goers commented on LOG4J2-1946: - I guess this isn't too surprising. The code is looking at the

[jira] [Commented] (LOG4J2-1946) DefaultRolloverStrategy is failing if some log file is deleted from the current sequence

[ https://issues.apache.org/jira/browse/LOG4J2-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054438#comment-16054438 ] Ralph Goers commented on LOG4J2-1946: - Your description was clear. The strategy is operating under

[jira] [Commented] (LOG4J2-1919) Change the appender of a logger will affect other loggers

[ https://issues.apache.org/jira/browse/LOG4J2-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023033#comment-16023033 ] Ralph Goers commented on LOG4J2-1919: - First, please read

[jira] [Commented] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023062#comment-16023062 ] Ralph Goers commented on LOG4J2-1185: - I can't verify that as I haven't looked into the problem with

  1   2   3   4   5   6   7   8   9   10   >