[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185675#comment-16185675 ] ASF GitHub Bot commented on LOG4J2-1216: GitHub user zsomborklara opened a pull request

[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=16182806#comment-16182806 ] Frederic Leitenberger commented on LOG4J2-1946: --- We have the same problem. Logger Config

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182760#comment-16182760 ] Matt Sicker commented on LOG4J2-1216: - Yes, your patch is still welcome! :) > Nested pattern lay

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182311#comment-16182311 ] Barna Zsombor Klara commented on LOG4J2-1216: - I think I ran into this issue recently

[jira] [Updated] (LOG4J2-2059) Refactor classes in core.net.ssl to allow non-KeyStore Providers

[ https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2059: Description: Refactor classes in the core.net.ssl package so that an SSL context can be created

[jira] [Updated] (LOG4J2-2059) Refactor classes in core.net.ssl to allow non-KeyStore Providers

[ https://issues.apache.org/jira/browse/LOG4J2-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2059: Priority: Minor (was: Major) > Refactor classes in core.net.ssl to allow non-KeyStore Provid

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181484#comment-16181484 ] Mikael Ståldal commented on LOG4J2-2056: I once made the log4j-liquibase module. Its code need

[jira] [Updated] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1694: --- Affects Version/s: 2.9.1 2.9.0 > Allow to easily add fie

[jira] [Commented] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

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

[jira] [Resolved] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1896. - Resolution: Fixed I created a separate ticket LOG4J2-2059 to deal with non-KeyStore based

[jira] [Created] (LOG4J2-2059) Refactor classes in core.net.ssl to allow non-KeyStore Providers

Remko Popma created LOG4J2-2059: --- Summary: Refactor classes in core.net.ssl to allow non-KeyStore Providers Key: LOG4J2-2059 URL: https://issues.apache.org/jira/browse/LOG4J2-2059 Project: Log4j 2

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180851#comment-16180851 ] Gary Gregory commented on LOG4J2-1896: -- The SSL and JMS CMs count on being able to reuse

[jira] [Comment Edited] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180775#comment-16180775 ] Remko Popma edited comment on LOG4J2-1896 at 9/26/17 2:01 PM: -- The most

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180775#comment-16180775 ] Remko Popma commented on LOG4J2-1896: - The most general interface for SSL seems

[jira] [Updated] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

[ https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dean Wookey updated LOG4J2-2058: Description: When using the JUL log manager, setting the java.locale.providers property to "

[jira] [Created] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

Dean Wookey created LOG4J2-2058: --- Summary: java.locale.providers set to HOST causes Log4j2 to crash in Java 9 Key: LOG4J2-2058 URL: https://issues.apache.org/jira/browse/LOG4J2-2058 Project: Log4j 2

[jira] [Updated] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

[ https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dean Wookey updated LOG4J2-2058: Description: When using the JUL log manager, setting the java.locale.providers property to "

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2056: Description: To fully support Java 9 all Log4j jars must (at least) be packaged as automatic

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2056: Description: To fully support Java 9 all Log4j jars must (at least) be packaged as automatic

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179761#comment-16179761 ] Ralph Goers commented on LOG4J2-2056: - [~scolebou...@joda.org] Thanks for taking a look. Your

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179640#comment-16179640 ] Stephen Colebourne commented on LOG4J2-2056: I've had a quick look. The api and log4j1.2 jars

[jira] [Updated] (LOG4J2-1944) Should suppress message "ERROR No log4j2 configuration file found..." when programmatic API is used to config log4j.

[ https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weian Deng updated LOG4J2-1944: --- Attachment: LOG4J2-1944.patch > Should suppress message "ERROR No log4j2 configuration fi

[jira] [Commented] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

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

[jira] [Closed] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-2054. --- Resolution: Fixed > Provide ways to configure SSL that avoid plain-text passwords in the lo

[jira] [Commented] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

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

[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=16178663#comment-16178663 ] Daan Hoogland edited comment on LOG4J2-1971 at 9/25/17 7:34 AM: People, I

[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=16178663#comment-16178663 ] Daan Hoogland commented on LOG4J2-1971: --- People, I am getting this outside OSGi context. I try

[jira] [Closed] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Berindei closed LOG4J2-2052. Verified on master, thanks! > Disable thread name caching by defa

[jira] [Commented] (LOG4J2-2057) Support SLF4J 1.8 binding mechanism

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

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178460#comment-16178460 ] Remko Popma commented on LOG4J2-1896: - (Note to self, still looking into this) Useful links: * http

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178266#comment-16178266 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 4:25 PM: -- Technically

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178268#comment-16178268 ] Matt Sicker commented on LOG4J2-2056: - Got it. Package names as listed right now LGTM. > Modular

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178266#comment-16178266 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 4:23 PM: -- Technically

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178266#comment-16178266 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 4:23 PM: -- Technically

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178266#comment-16178266 ] Ralph Goers commented on LOG4J2-2056: - Technically they could but I would find that confusing since

[jira] [Created] (LOG4J2-2057) Support SLF4J 1.8 binding mechanism

Ralph Goers created LOG4J2-2057: --- Summary: Support SLF4J 1.8 binding mechanism Key: LOG4J2-2057 URL: https://issues.apache.org/jira/browse/LOG4J2-2057 Project: Log4j 2 Issue Type: Improvement

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178239#comment-16178239 ] Ralph Goers commented on LOG4J2-2056: - OK. I changed the table. > Modularize Log4j as automa

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2056: Description: To fully support Java 9 all Log4j jars must (at least) be packaged as automatic

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178222#comment-16178222 ] Gary Gregory commented on LOG4J2-2056: -- I kind of like the dot matching the dash in "t

[jira] [Updated] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2054: Description: Following up on LOG4J2-1896, currently SecureSocketAppender can only be configured

[jira] [Updated] (LOG4J2-2054) Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2054: Summary: Provide ways to configure SSL that avoid plain-text passwords in the log4j configuration

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

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

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

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

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178143#comment-16178143 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 10:34 AM

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178143#comment-16178143 ] Ralph Goers edited comment on LOG4J2-2056 at 9/24/17 10:32 AM

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178143#comment-16178143 ] Ralph Goers commented on LOG4J2-2056: - If they want to release Log4J 1 then they would use the same

[jira] [Resolved] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-2052. - Resolution: Fixed Fix Version/s: 2.10.0 Fixed in master. Please verify and close

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

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

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178121#comment-16178121 ] Remko Popma commented on LOG4J2-2056: - Is it a good idea to use the below? |log4j-1.2-api

[jira] [Created] (LOG4J2-2056) Modularize Log4j as automatic modules

Ralph Goers created LOG4J2-2056: --- Summary: Modularize Log4j as automatic modules Key: LOG4J2-2056 URL: https://issues.apache.org/jira/browse/LOG4J2-2056 Project: Log4j 2 Issue Type: New

[jira] [Closed] (LOG4J2-2055) ServiceConfigurationError in Tomcat when Log4j is used as the logging implementation

[ https://issues.apache.org/jira/browse/LOG4J2-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2055. --- Resolution: Fixed Fix Version/s: 2.9.2 > ServiceConfigurationError in Tomcat when Lo

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178019#comment-16178019 ] Remko Popma commented on LOG4J2-2054: - Thanks for the good feedback! I've reopened LOG4J2-1896

[jira] [Reopened] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1896: - As per discussion in LOG4J2-2054, I will replace the {{PasswordProvider}} interface with a generic

[jira] [Commented] (LOG4J2-2055) ServiceConfigurationError in Tomcat when Log4j is used as the logging implementation

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

[jira] [Created] (LOG4J2-2055) ServiceConfigurationError in Tomcat when Log4j is used as the logging implementation

Ralph Goers created LOG4J2-2055: --- Summary: ServiceConfigurationError in Tomcat when Log4j is used as the logging implementation Key: LOG4J2-2055 URL: https://issues.apache.org/jira/browse/LOG4J2-2055

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178007#comment-16178007 ] Ralph Goers commented on LOG4J2-2054: - That would make sense to me. > Provide alternati

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178006#comment-16178006 ] Gary Gregory commented on LOG4J2-2054: -- Do we want to go as far as having a generic SecretProvider

[jira] [Comment Edited] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177982#comment-16177982 ] Ralph Goers edited comment on LOG4J2-2054 at 9/23/17 9:34 PM: -- FWIW

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177982#comment-16177982 ] Ralph Goers commented on LOG4J2-2054: - FWIW, The FlumeAppender uses

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177919#comment-16177919 ] Gary Gregory commented on LOG4J2-2054: -- I do not think so. Java works with KeyStore/TrustStore, I am

[jira] [Commented] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

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

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177901#comment-16177901 ] Remko Popma commented on LOG4J2-2054: - That is certainly another option. I haven't looked

[jira] [Commented] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177871#comment-16177871 ] Gary Gregory commented on LOG4J2-2054: -- Passwords could also be fetched from Maven's password vault

[jira] [Updated] (LOG4J2-2054) Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords in config

[ https://issues.apache.org/jira/browse/LOG4J2-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2054: Summary: Provide alternatives to configuring SecureSocketAppender that avoid plain-text passwords

[jira] [Created] (LOG4J2-2054) Provide alternative to configuring SecureSocketAppender to avoid plain-text passwords in config

Remko Popma created LOG4J2-2054: --- Summary: Provide alternative to configuring SecureSocketAppender to avoid plain-text passwords in config Key: LOG4J2-2054 URL: https://issues.apache.org/jira/browse/LOG4J2-2054

[jira] [Updated] (LOG4J2-1896) Update classes in org.apache.logging.log4j.core.net.ssl in APIs from String to char[] for passwords

[ https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1896: Fix Version/s: (was: 2.9.1) 2.10.0 > Update clas

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177466#comment-16177466 ] Remko Popma commented on LOG4J2-2052: - Actually I just realized this can be as simple as {code

[jira] [Updated] (LOG4J2-2053) Exception java.nio.charset.UnsupportedCharsetException: cp65001 in 2.9.0

[ https://issues.apache.org/jira/browse/LOG4J2-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Steudle updated LOG4J2-2053: -- Description: Today I updated my fitnesse project to use the 2.9.0 versions of log4-core

[jira] [Commented] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176087#comment-16176087 ] Remko Popma commented on LOG4J2-2035: - >From Log4j 2.9, async loggers now require LMAX Disrup

[jira] [Commented] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

[ https://issues.apache.org/jira/browse/LOG4J2-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176076#comment-16176076 ] Corneliu C commented on LOG4J2-2035: Hi, any reasons for not using latest version 3.3.6? Thanks

[jira] [Commented] (LOG4J2-2035) There is no such lib as disruptor-3.3.3

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

[jira] [Closed] (LOG4J2-1914) AsyncLogger and message formatting (ConcurrentModificationException)

[ https://issues.apache.org/jira/browse/LOG4J2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker closed LOG4J2-1914. --- > AsyncLogger and message formatting (ConcurrentModificationExcept

[jira] [Commented] (LOG4J2-1914) AsyncLogger and message formatting (ConcurrentModificationException)

[ https://issues.apache.org/jira/browse/LOG4J2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173611#comment-16173611 ] Leon Finker commented on LOG4J2-1914: - Thank you for looking at this! Unfortunately I was not able

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

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

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

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

[jira] [Resolved] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-2031. - Resolution: Fixed Fixed in master. Please verify and close. > Messages appear out of or

[jira] [Updated] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2031: Affects Version/s: 2.9.1 > Messages appear out of order in log file (was: Log4j2 log f

[jira] [Updated] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-2031: Fix Version/s: 2.10.0 > Messages appear out of order in log file (was: Log4j2 log f

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

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

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

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

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

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

[jira] [Assigned] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-2052: --- Assignee: Remko Popma > Disable thread name caching by defa

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169468#comment-16169468 ] Remko Popma commented on LOG4J2-2052: - I would prefer to keep the default as is, and this may be one

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169415#comment-16169415 ] Dan Berindei commented on LOG4J2-2052: -- Sure, I'm fine with changing it only on 8u102+. > Disa

[jira] [Closed] (LOG4J2-1926) Remove dependency on RMI and Management APIs from log4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1926. -- Resolution: Fixed > Remove dependency on RMI and Management APIs from log4j-

[jira] [Updated] (LOG4J2-1889) Move KafkaAppender to new module

[ https://issues.apache.org/jira/browse/LOG4J2-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1889: --- Affects Version/s: 2.9.0 > Move KafkaAppender to new mod

[jira] [Updated] (LOG4J2-1926) Remove dependency on RMI and Management APIs from log4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1926: --- Labels: Android (was: ) > Remove dependency on RMI and Management APIs from log4j-

[jira] [Reopened] (LOG4J2-1926) Remove dependency on RMI and Management APIs from log4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reopened LOG4J2-1926: > Remove dependency on RMI and Management APIs from log4j-

[jira] [Closed] (LOG4J2-1959) Disable DTD processing in XML configuration files

[ https://issues.apache.org/jira/browse/LOG4J2-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1959. -- > Disable DTD processing in XML configuration fi

[jira] [Comment Edited] (LOG4J2-2051) Update Conversant Disruptor from 1.2.10 to 1.2.11.

[ https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168945#comment-16168945 ] Gary Gregory edited comment on LOG4J2-2051 at 9/16/17 3:18 PM: --- I guess. We

[jira] [Commented] (LOG4J2-2051) Update Conversant Disruptor from 1.2.10 to 1.2.11.

[ https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168945#comment-16168945 ] Gary Gregory commented on LOG4J2-2051: -- I guess. We could also create a Java 8 JIRA "

[jira] [Commented] (LOG4J2-2051) Update Conversant Disruptor from 1.2.10 to 1.2.11.

[ https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168821#comment-16168821 ] Remko Popma commented on LOG4J2-2051: - Should we leave this ticket open, or resolve

[jira] [Updated] (LOG4J2-2051) Update Conversant Disruptor from 1.2.10 to 1.2.11.

[ https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2051: - Labels: Java8 (was: ) > Update Conversant Disruptor from 1.2.10 to 1.2

[jira] [Commented] (LOG4J2-2051) Update Conversant Disruptor from 1.2.10 to 1.2.11.

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

[jira] [Comment Edited] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168210#comment-16168210 ] Remko Popma edited comment on LOG4J2-2052 at 9/15/17 5:16 PM: -- I wasn't

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168210#comment-16168210 ] Remko Popma commented on LOG4J2-2052: - I wasn't aware of that fix. We could try to detect the Java

[jira] [Created] (LOG4J2-2052) Disable thread name caching by default

Dan Berindei created LOG4J2-2052: Summary: Disable thread name caching by default Key: LOG4J2-2052 URL: https://issues.apache.org/jira/browse/LOG4J2-2052 Project: Log4j 2 Issue Type

[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=16168059#comment-16168059 ] Remko Popma edited comment on LOG4J2-1988 at 9/15/17 3:52 PM: -- Fixed

[jira] [Resolved] (LOG4J2-1914) AsyncLogger and message formatting (ConcurrentModificationException)

[ https://issues.apache.org/jira/browse/LOG4J2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1914. - Resolution: Fixed Fix Version/s: 2.9.1 Fixed in master. I was able to add a test

[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=16168057#comment-16168057 ] ASF subversion and git services commented on LOG4J2-1988: - Commit

<    1   2   3   4   5   6   7   8   9   10   >