[jira] [Commented] (LOG4J2-1879) Update Jansi from 1.14 to 1.15
[ https://issues.apache.org/jira/browse/LOG4J2-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965100#comment-15965100 ] ASF subversion and git services commented on LOG4J2-1879: - Commit b511ecf011dfff5d9d326a762ae8956c4935ce8c in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=b511ecf ] [LOG4J2-1879] Update JAnsi from 1.14 to 1.15. > Update Jansi from 1.14 to 1.15 > -- > > Key: LOG4J2-1879 > URL: https://issues.apache.org/jira/browse/LOG4J2-1879 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update Jansi from 1.14 to 1.15 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1867) jackson-databind dependency missing in the configuration document
[ https://issues.apache.org/jira/browse/LOG4J2-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964586#comment-15964586 ] ASF subversion and git services commented on LOG4J2-1867: - Commit a8fdb4ee5c19bd84fd8898d56a00cc68c9b8e2b6 in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a8fdb4e ] LOG4J2-1867 Fix configuration documentation > jackson-databind dependency missing in the configuration document > - > > Key: LOG4J2-1867 > URL: https://issues.apache.org/jira/browse/LOG4J2-1867 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Affects Versions: 2.8.1 >Reporter: James Jithin >Assignee: Mikael Ståldal > Fix For: 2.9 > > > Was following the link: > http://logging.apache.org/log4j/2.x/manual/configuration.html > to configure log4j2 with yaml. > The following links: > http://logging.apache.org/log4j/2.x/maven-artifacts.html > http://logging.apache.org/log4j/2.x/manual/configuration.html#YAML > asks to import the following dependencies: > > > org.apache.logging.log4j > log4j-api > 2.8.1 > > > org.apache.logging.log4j > log4j-core > 2.8.1 > > > > com.fasterxml.jackson.dataformat > jackson-dataformat-yaml > 2.8.6 > > But not > > com.fasterxml.jackson.core > jackson-databind > > which is a requirement. > Enabling debug mode didn't point out about missing classes > com.fasterxml.jackson.databind.ObjectMapper and > com.fasterxml.jackson.databind.JsonNode which are mentioned in > YamlConfigurationFactory. Such messages on missing classes is really going to > help in resolving issues at the earliest. Please add the missing dependency > to the YAML section. I see that it is provided for JSON configuration, but > missed for YAML. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1876) Unreliable checking for runtime dependencies
[
https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964580#comment-15964580
]
ASF subversion and git services commented on LOG4J2-1876:
-
Commit b04e5a7eed22a9f1e66c1a378bec6c2d57cd1cbf in logging-log4j2's branch
refs/heads/master from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=b04e5a7 ]
LOG4J2-1876 More reliable checking for runtime dependencies
> Unreliable checking for runtime dependencies
>
>
> Key: LOG4J2-1876
> URL: https://issues.apache.org/jira/browse/LOG4J2-1876
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.8.2
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.9
>
>
> If I include this in Maven POM:
> {code}
>
> com.fasterxml.jackson.core
> jackson-databind
> 2.8.7
> runtime
>
>
> com.fasterxml.jackson.core
> jackson-core
>
>
>
> {code}
> I get this printed on STDERR on startup:
> {code}
> Unknown error checking for existence of class:
> com.fasterxml.jackson.databind.ObjectMapper
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/Versioned
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.logging.log4j.util.LoaderUtil.loadClass(LoaderUtil.java:141)
> at
> org.apache.logging.log4j.util.LoaderUtil.isClassAvailable(LoaderUtil.java:115)
> at
> org.apache.logging.log4j.core.util.Loader.isClassAvailable(Loader.java:310)
> at
> org.apache.logging.log4j.core.config.yaml.YamlConfigurationFactory.(YamlConfigurationFactory.java:47)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.logging.log4j.core.util.ReflectionUtil.instantiate(ReflectionUtil.java:188)
> at
> org.apache.logging.log4j.core.config.ConfigurationFactory.addFactory(ConfigurationFactory.java:190)
> at
> org.apache.logging.log4j.core.config.ConfigurationFactory.getInstance(ConfigurationFactory.java:164)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:613)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:242)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:174)
> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:618)
> at logtest.Main.(Main.java:14)
> Caused by: java.lang.ClassNotFoundException:
> com.fasterxml.jackson.core.Versioned
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 33 more
> Unknown error checking for existence of class:
> com.fasterxml.jackson.databind.ObjectMapper
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/Versioned
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at
[jira] [Commented] (LOG4J2-1867) jackson-databind dependency missing in the configuration document
[ https://issues.apache.org/jira/browse/LOG4J2-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964546#comment-15964546 ] ASF subversion and git services commented on LOG4J2-1867: - Commit 024acaf3e30a59c746506f9c9d92083fb3a35325 in logging-log4j2's branch refs/heads/java9NoMultiRelease from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=024acaf ] LOG4J2-1867 Fix JSON and YAML config examples and dependency info > jackson-databind dependency missing in the configuration document > - > > Key: LOG4J2-1867 > URL: https://issues.apache.org/jira/browse/LOG4J2-1867 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Affects Versions: 2.8.1 >Reporter: James Jithin >Assignee: Mikael Ståldal > Fix For: 2.9 > > > Was following the link: > http://logging.apache.org/log4j/2.x/manual/configuration.html > to configure log4j2 with yaml. > The following links: > http://logging.apache.org/log4j/2.x/maven-artifacts.html > http://logging.apache.org/log4j/2.x/manual/configuration.html#YAML > asks to import the following dependencies: > > > org.apache.logging.log4j > log4j-api > 2.8.1 > > > org.apache.logging.log4j > log4j-core > 2.8.1 > > > > com.fasterxml.jackson.dataformat > jackson-dataformat-yaml > 2.8.6 > > But not > > com.fasterxml.jackson.core > jackson-databind > > which is a requirement. > Enabling debug mode didn't point out about missing classes > com.fasterxml.jackson.databind.ObjectMapper and > com.fasterxml.jackson.databind.JsonNode which are mentioned in > YamlConfigurationFactory. Such messages on missing classes is really going to > help in resolving issues at the earliest. Please add the missing dependency > to the YAML section. I see that it is provided for JSON configuration, but > missed for YAML. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1867) jackson-databind dependency missing in the configuration document
[ https://issues.apache.org/jira/browse/LOG4J2-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964241#comment-15964241 ] ASF subversion and git services commented on LOG4J2-1867: - Commit 024acaf3e30a59c746506f9c9d92083fb3a35325 in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=024acaf ] LOG4J2-1867 Fix JSON and YAML config examples and dependency info > jackson-databind dependency missing in the configuration document > - > > Key: LOG4J2-1867 > URL: https://issues.apache.org/jira/browse/LOG4J2-1867 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Affects Versions: 2.8.1 >Reporter: James Jithin >Assignee: Mikael Ståldal > > Was following the link: > http://logging.apache.org/log4j/2.x/manual/configuration.html > to configure log4j2 with yaml. > The following links: > http://logging.apache.org/log4j/2.x/maven-artifacts.html > http://logging.apache.org/log4j/2.x/manual/configuration.html#YAML > asks to import the following dependencies: > > > org.apache.logging.log4j > log4j-api > 2.8.1 > > > org.apache.logging.log4j > log4j-core > 2.8.1 > > > > com.fasterxml.jackson.dataformat > jackson-dataformat-yaml > 2.8.6 > > But not > > com.fasterxml.jackson.core > jackson-databind > > which is a requirement. > Enabling debug mode didn't point out about missing classes > com.fasterxml.jackson.databind.ObjectMapper and > com.fasterxml.jackson.databind.JsonNode which are mentioned in > YamlConfigurationFactory. Such messages on missing classes is really going to > help in resolving issues at the earliest. Please add the missing dependency > to the YAML section. I see that it is provided for JSON configuration, but > missed for YAML. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module
[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962913#comment-15962913 ] ASF subversion and git services commented on LOG4J2-1851: - Commit 394c30f594c9eac570a43313bf44be4bc60cded9 in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=394c30f ] Merge branch 'master' into LOG4J2-1851 # Conflicts: # src/changes/changes.xml > Move org.apache.logging.log4j.core.net.server package to new module > --- > > Key: LOG4J2-1851 > URL: https://issues.apache.org/jira/browse/LOG4J2-1851 > Project: Log4j 2 > Issue Type: Sub-task > Components: Core >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > Move the SocketServer stuff in org.apache.logging.log4j.core.net.server > package to a new module. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module
[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962912#comment-15962912 ] ASF subversion and git services commented on LOG4J2-1851: - Commit 6fd6dfcd7fa772ffa1a4d3c9c783b5b0af7501d9 in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=6fd6dfc ] Merge branch 'master' into LOG4J2-1851 > Move org.apache.logging.log4j.core.net.server package to new module > --- > > Key: LOG4J2-1851 > URL: https://issues.apache.org/jira/browse/LOG4J2-1851 > Project: Log4j 2 > Issue Type: Sub-task > Components: Core >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > Move the SocketServer stuff in org.apache.logging.log4j.core.net.server > package to a new module. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module
[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962911#comment-15962911 ] ASF subversion and git services commented on LOG4J2-1851: - Commit 873e7efbab22aac29e29716a871ff114c60202bd in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=873e7ef ] Merge branch 'master' into LOG4J2-1851 > Move org.apache.logging.log4j.core.net.server package to new module > --- > > Key: LOG4J2-1851 > URL: https://issues.apache.org/jira/browse/LOG4J2-1851 > Project: Log4j 2 > Issue Type: Sub-task > Components: Core >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > Move the SocketServer stuff in org.apache.logging.log4j.core.net.server > package to a new module. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
[
https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962614#comment-15962614
]
ASF subversion and git services commented on LOG4J2-1860:
-
Commit f64ea4b597ee6cef22c99ed5f382489ff87431c8 in logging-log4j2's branch
refs/heads/LOG4J2-1851 from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f64ea4b ]
Merge branch 'master' into LOG4J2-1860
> Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1860
> URL: https://issues.apache.org/jira/browse/LOG4J2-1860
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
>Affects Versions: 2.8.1
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> It would be nice to have shortcuts for
> {code}
> builder.addComponent(builder.newComponent("my-name, "Property", "my-value"));
> {code}
> and
> {code}
> builder.addComponent(builder.newComponent("KeyValuePair").addAttribute("key",
> "my-key").addAttribute("value", "my-value"));
> {code}
> since they are used by several appenders and layouts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module
[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962615#comment-15962615 ] ASF subversion and git services commented on LOG4J2-1851: - Commit 394c30f594c9eac570a43313bf44be4bc60cded9 in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=394c30f ] Merge branch 'master' into LOG4J2-1851 # Conflicts: # src/changes/changes.xml > Move org.apache.logging.log4j.core.net.server package to new module > --- > > Key: LOG4J2-1851 > URL: https://issues.apache.org/jira/browse/LOG4J2-1851 > Project: Log4j 2 > Issue Type: Sub-task > Components: Core >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > Move the SocketServer stuff in org.apache.logging.log4j.core.net.server > package to a new module. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1872) Update JavaMail from 1.5.5 to 1.5.6
[ https://issues.apache.org/jira/browse/LOG4J2-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962613#comment-15962613 ] ASF subversion and git services commented on LOG4J2-1872: - Commit c4b4836fb91b453aa4eb907b2821dca4057051cc in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c4b4836 ] [LOG4J2-1872 Update JavaMail from 1.5.5 to 1.5.6. > Update JavaMail from 1.5.5 to 1.5.6 > --- > > Key: LOG4J2-1872 > URL: https://issues.apache.org/jira/browse/LOG4J2-1872 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update JavaMail from 1.5.5 to 1.5.6. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0
[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962611#comment-15962611 ] ASF subversion and git services commented on LOG4J2-1869: - Commit 49e843f2d916139fe3fc2ea8921e0dd8363dee96 in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=49e843f ] [LOG4J2-1869] Update Kafka client from 0.10.1.1 to 0.10.2.0. > Update Kafka client from 0.10.1.1 to 0.10.2.0 > - > > Key: LOG4J2-1869 > URL: https://issues.apache.org/jira/browse/LOG4J2-1869 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update Kafka client from 0.10.1.1 to 0.10.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0
[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962612#comment-15962612 ] ASF subversion and git services commented on LOG4J2-1869: - Commit ef7f7241fb4aefe7614363e5d284c31c4f0d in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ef7f724 ] [LOG4J2-1869] Update Kafka client from 0.10.1.1 to 0.10.2.0. > Update Kafka client from 0.10.1.1 to 0.10.2.0 > - > > Key: LOG4J2-1869 > URL: https://issues.apache.org/jira/browse/LOG4J2-1869 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update Kafka client from 0.10.1.1 to 0.10.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1868) Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0
[ https://issues.apache.org/jira/browse/LOG4J2-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962610#comment-15962610 ] ASF subversion and git services commented on LOG4J2-1868: - Commit ccc30dc09d7dc0e7fe3db05dc7e5f7a086b8f21c in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ccc30dc ] [LOG4J2-1868] Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0. Local build OK > Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0 > -- > > Key: LOG4J2-1868 > URL: https://issues.apache.org/jira/browse/LOG4J2-1868 > Project: Log4j 2 > Issue Type: Improvement >Affects Versions: 2.8.2 >Reporter: Gary Gregory > Fix For: 2.9 > > > Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
[
https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962603#comment-15962603
]
ASF subversion and git services commented on LOG4J2-1860:
-
Commit df1b3e8846246988d6119f65e7fcb3e5a9a3f1cb in logging-log4j2's branch
refs/heads/master from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=df1b3e8 ]
LOG4J2-1860 Shortcut to add Property and KeyValuePair component in
ConfigurationBuilder
> Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1860
> URL: https://issues.apache.org/jira/browse/LOG4J2-1860
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
>Affects Versions: 2.8.1
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> It would be nice to have shortcuts for
> {code}
> builder.addComponent(builder.newComponent("my-name, "Property", "my-value"));
> {code}
> and
> {code}
> builder.addComponent(builder.newComponent("KeyValuePair").addAttribute("key",
> "my-key").addAttribute("value", "my-value"));
> {code}
> since they are used by several appenders and layouts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
[
https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962604#comment-15962604
]
ASF subversion and git services commented on LOG4J2-1860:
-
Commit f64ea4b597ee6cef22c99ed5f382489ff87431c8 in logging-log4j2's branch
refs/heads/master from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f64ea4b ]
Merge branch 'master' into LOG4J2-1860
> Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1860
> URL: https://issues.apache.org/jira/browse/LOG4J2-1860
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
>Affects Versions: 2.8.1
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> It would be nice to have shortcuts for
> {code}
> builder.addComponent(builder.newComponent("my-name, "Property", "my-value"));
> {code}
> and
> {code}
> builder.addComponent(builder.newComponent("KeyValuePair").addAttribute("key",
> "my-key").addAttribute("value", "my-value"));
> {code}
> since they are used by several appenders and layouts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0
[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962600#comment-15962600 ] ASF subversion and git services commented on LOG4J2-1869: - Commit ef7f7241fb4aefe7614363e5d284c31c4f0d in logging-log4j2's branch refs/heads/LOG4J2-1860 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ef7f724 ] [LOG4J2-1869] Update Kafka client from 0.10.1.1 to 0.10.2.0. > Update Kafka client from 0.10.1.1 to 0.10.2.0 > - > > Key: LOG4J2-1869 > URL: https://issues.apache.org/jira/browse/LOG4J2-1869 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update Kafka client from 0.10.1.1 to 0.10.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1872) Update JavaMail from 1.5.5 to 1.5.6
[ https://issues.apache.org/jira/browse/LOG4J2-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962601#comment-15962601 ] ASF subversion and git services commented on LOG4J2-1872: - Commit c4b4836fb91b453aa4eb907b2821dca4057051cc in logging-log4j2's branch refs/heads/LOG4J2-1860 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c4b4836 ] [LOG4J2-1872 Update JavaMail from 1.5.5 to 1.5.6. > Update JavaMail from 1.5.5 to 1.5.6 > --- > > Key: LOG4J2-1872 > URL: https://issues.apache.org/jira/browse/LOG4J2-1872 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update JavaMail from 1.5.5 to 1.5.6. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
[
https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962602#comment-15962602
]
ASF subversion and git services commented on LOG4J2-1860:
-
Commit f64ea4b597ee6cef22c99ed5f382489ff87431c8 in logging-log4j2's branch
refs/heads/LOG4J2-1860 from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f64ea4b ]
Merge branch 'master' into LOG4J2-1860
> Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1860
> URL: https://issues.apache.org/jira/browse/LOG4J2-1860
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
>Affects Versions: 2.8.1
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>
> It would be nice to have shortcuts for
> {code}
> builder.addComponent(builder.newComponent("my-name, "Property", "my-value"));
> {code}
> and
> {code}
> builder.addComponent(builder.newComponent("KeyValuePair").addAttribute("key",
> "my-key").addAttribute("value", "my-value"));
> {code}
> since they are used by several appenders and layouts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0
[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962599#comment-15962599 ] ASF subversion and git services commented on LOG4J2-1869: - Commit 49e843f2d916139fe3fc2ea8921e0dd8363dee96 in logging-log4j2's branch refs/heads/LOG4J2-1860 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=49e843f ] [LOG4J2-1869] Update Kafka client from 0.10.1.1 to 0.10.2.0. > Update Kafka client from 0.10.1.1 to 0.10.2.0 > - > > Key: LOG4J2-1869 > URL: https://issues.apache.org/jira/browse/LOG4J2-1869 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update Kafka client from 0.10.1.1 to 0.10.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1868) Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0
[ https://issues.apache.org/jira/browse/LOG4J2-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962598#comment-15962598 ] ASF subversion and git services commented on LOG4J2-1868: - Commit ccc30dc09d7dc0e7fe3db05dc7e5f7a086b8f21c in logging-log4j2's branch refs/heads/LOG4J2-1860 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ccc30dc ] [LOG4J2-1868] Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0. Local build OK > Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0 > -- > > Key: LOG4J2-1868 > URL: https://issues.apache.org/jira/browse/LOG4J2-1868 > Project: Log4j 2 > Issue Type: Improvement >Affects Versions: 2.8.2 >Reporter: Gary Gregory > Fix For: 2.9 > > > Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1872) Update JavaMail from 1.5.5 to 1.5.6
[ https://issues.apache.org/jira/browse/LOG4J2-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962397#comment-15962397 ] ASF subversion and git services commented on LOG4J2-1872: - Commit c4b4836fb91b453aa4eb907b2821dca4057051cc in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c4b4836 ] [LOG4J2-1872 Update JavaMail from 1.5.5 to 1.5.6. > Update JavaMail from 1.5.5 to 1.5.6 > --- > > Key: LOG4J2-1872 > URL: https://issues.apache.org/jira/browse/LOG4J2-1872 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > > Update JavaMail from 1.5.5 to 1.5.6. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0
[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962396#comment-15962396 ] ASF subversion and git services commented on LOG4J2-1869: - Commit ef7f7241fb4aefe7614363e5d284c31c4f0d in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ef7f724 ] [LOG4J2-1869] Update Kafka client from 0.10.1.1 to 0.10.2.0. > Update Kafka client from 0.10.1.1 to 0.10.2.0 > - > > Key: LOG4J2-1869 > URL: https://issues.apache.org/jira/browse/LOG4J2-1869 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.9 > > > Update Kafka client from 0.10.1.1 to 0.10.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0
[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962303#comment-15962303 ] ASF subversion and git services commented on LOG4J2-1869: - Commit 49e843f2d916139fe3fc2ea8921e0dd8363dee96 in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=49e843f ] [LOG4J2-1869] Update Kafka client from 0.10.1.1 to 0.10.2.0. > Update Kafka client from 0.10.1.1 to 0.10.2.0 > - > > Key: LOG4J2-1869 > URL: https://issues.apache.org/jira/browse/LOG4J2-1869 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.2 >Reporter: Gary Gregory > > Update Kafka client from 0.10.1.1 to 0.10.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
[
https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957107#comment-15957107
]
ASF subversion and git services commented on LOG4J2-1860:
-
Commit df1b3e8846246988d6119f65e7fcb3e5a9a3f1cb in logging-log4j2's branch
refs/heads/LOG4J2-1860 from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=df1b3e8 ]
LOG4J2-1860 Shortcut to add Property and KeyValuePair component in
ConfigurationBuilder
> Shortcut to add Property and KeyValuePair component in ConfigurationBuilder
> ---
>
> Key: LOG4J2-1860
> URL: https://issues.apache.org/jira/browse/LOG4J2-1860
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
>Affects Versions: 2.8.1
>Reporter: Mikael Ståldal
>
> It would be nice to have shortcuts for
> {code}
> builder.addComponent(builder.newComponent("my-name, "Property", "my-value"));
> {code}
> and
> {code}
> builder.addComponent(builder.newComponent("KeyValuePair").addAttribute("key",
> "my-key").addAttribute("value", "my-value"));
> {code}
> since they are used by several appenders and layouts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[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=15953023#comment-15953023 ] ASF subversion and git services commented on LOG4J2-1359: - Commit 34552d7d725c3b7547e1c19f6ce803b83c60bd94 in logging-log4j2's branch refs/heads/java9NoMultiRelease from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=34552d7 ] LOG4J2-1359 - Set up for modules. Do not use multi-release jars > Add support for Java 9 StackWalker API in ReflectionUtil > > > Key: LOG4J2-1359 > URL: https://issues.apache.org/jira/browse/LOG4J2-1359 > Project: Log4j 2 > Issue Type: Improvement > Components: API > Environment: Java 1.9+ >Reporter: Matt Sicker >Assignee: Ralph Goers > Labels: jdk9 > > [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html] > Based on the functional nature of this API, supporting it may require > compiling at least one class using javac 1.9 and reflectively loading it in > ReflectionUtil similar to how Spring supports newer JDK APIs. > Without support for StackWalker, ReflectionUtil will fall back to using a > slower API in Java 1.9. This is because the Reflection class is a > sun-internal class which are no longer exported to non-JDK code without > setting special command line flags. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1862) The comments in Order and OrderComparator are wrong
[ https://issues.apache.org/jira/browse/LOG4J2-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952788#comment-15952788 ] ASF subversion and git services commented on LOG4J2-1862: - Commit 3bc94c0bbe07719affb38c08124bd917a061d3fa in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=3bc94c0 ] Merge commit 'refs/pull/69/head' of https://github.com/apache/logging-log4j2 Related to LOG4J2-1862. > The comments in Order and OrderComparator are wrong > --- > > Key: LOG4J2-1862 > URL: https://issues.apache.org/jira/browse/LOG4J2-1862 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: wangyuntao >Priority: Trivial > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1861) Fix JavaDoc on org.apache.logging.log4j.ThreadContext (about inheritance)
[
https://issues.apache.org/jira/browse/LOG4J2-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952785#comment-15952785
]
ASF subversion and git services commented on LOG4J2-1861:
-
Commit 000de2cde6a745c945e7575313ac6fbe841a4b49 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=000de2c ]
[LOG4J2-1861] Fix ThreadContext javadoc about inheritance
> Fix JavaDoc on org.apache.logging.log4j.ThreadContext (about inheritance)
> -
>
> Key: LOG4J2-1861
> URL: https://issues.apache.org/jira/browse/LOG4J2-1861
> Project: Log4j 2
> Issue Type: Documentation
> Components: API
>Affects Versions: 2.8.1
>Reporter: Franz van Betteraey
>Assignee: Matt Sicker
>Priority: Trivial
> Labels: easyfix, javadoc
> Fix For: 2.8.2
>
>
> The
> [JavaDoc|https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/ThreadContext.html]
> of org.apache.logging.log4j.ThreadContext describes the behavior regarding
> inheritance as follows:
> {quote}
> A child thread automatically inherits a copy of the mapped diagnostic context
> of its parent.
> {quote}
> But the behavior was changed in LOG4J2-479. Now the system property
> _isThreadContextMapInheritable_ has to be set to _true_ to enforce this
> behavior (see
> [documentation|https://logging.apache.org/log4j/2.x/manual/thread-context.html]).
> This should be corrected in the JavaDoc of ThreadContext.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1863) Add support for filtering input in TcpSocketServer and UdpSocketServer
[ https://issues.apache.org/jira/browse/LOG4J2-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15952781#comment-15952781 ] ASF subversion and git services commented on LOG4J2-1863: - Commit 5dcc19215827db29c993d0305ee2b0d8dd05939d in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=5dcc192 ] [LOG4J2-1863] Add class filtering to AbstractSocketServer This allows a whitelist of class names to be specified to configure which classes are allowed to be deserialized in both TcpSocketServer and UdpSocketServer. > Add support for filtering input in TcpSocketServer and UdpSocketServer > -- > > Key: LOG4J2-1863 > URL: https://issues.apache.org/jira/browse/LOG4J2-1863 > Project: Log4j 2 > Issue Type: New Feature > Components: Receivers >Affects Versions: 2.8.1 >Reporter: Matt Sicker >Assignee: Matt Sicker > Fix For: 2.8.2 > > > It is best practice to add a configurable class filter to ObjectInputStream > usage when input comes from untrusted sources. Add this feature to > TcpSocketServer and UdpSocketServer along with sensible default settings. > This feature is unnecessary in JmsServer as that relies on the underlying > configuration of the JMS server (e.g., ActiveMQ has a similar configuration > option). -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module
[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943204#comment-15943204 ] ASF subversion and git services commented on LOG4J2-1851: - Commit 6fd6dfcd7fa772ffa1a4d3c9c783b5b0af7501d9 in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=6fd6dfc ] Merge branch 'master' into LOG4J2-1851 > Move org.apache.logging.log4j.core.net.server package to new module > --- > > Key: LOG4J2-1851 > URL: https://issues.apache.org/jira/browse/LOG4J2-1851 > Project: Log4j 2 > Issue Type: Sub-task > Components: Core >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > Move the SocketServer stuff in org.apache.logging.log4j.core.net.server > package to a new module. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1856) Update Jackson from 2.8.6 to 2.8.7.
[ https://issues.apache.org/jira/browse/LOG4J2-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943203#comment-15943203 ] ASF subversion and git services commented on LOG4J2-1856: - Commit 5aff929bb44e63c0dbf0cdc7cfb5d5fbd50660ef in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=5aff929 ] [LOG4J2-1856] Update Jackson from 2.8.6 to 2.8.7. > Update Jackson from 2.8.6 to 2.8.7. > --- > > Key: LOG4J2-1856 > URL: https://issues.apache.org/jira/browse/LOG4J2-1856 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.1 >Reporter: Gary Gregory > Fix For: 2.8.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1853) The default value of RandomAccessFileAppender.Builder append field is wrong
[ https://issues.apache.org/jira/browse/LOG4J2-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943201#comment-15943201 ] ASF subversion and git services commented on LOG4J2-1853: - Commit 03e9743e8607f27e6f54d9009404d6c2c5228259 in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=03e9743 ] [LOG4J2-1853] The default value of RandomAccessFileAppender.Builder append field is wrong. > The default value of RandomAccessFileAppender.Builder append field is wrong > --- > > Key: LOG4J2-1853 > URL: https://issues.apache.org/jira/browse/LOG4J2-1853 > Project: Log4j 2 > Issue Type: Bug >Reporter: wangyuntao > Fix For: 2.8.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1856) Update Jackson from 2.8.6 to 2.8.7.
[ https://issues.apache.org/jira/browse/LOG4J2-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943202#comment-15943202 ] ASF subversion and git services commented on LOG4J2-1856: - Commit bd16bfe48ecc0fc3119e412f8e8e98398fddf571 in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=bd16bfe ] [LOG4J2-1856] Update Jackson from 2.8.6 to 2.8.7. > Update Jackson from 2.8.6 to 2.8.7. > --- > > Key: LOG4J2-1856 > URL: https://issues.apache.org/jira/browse/LOG4J2-1856 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.1 >Reporter: Gary Gregory > Fix For: 2.8.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1856) Update Jackson from 2.8.6 to 2.8.7.
[ https://issues.apache.org/jira/browse/LOG4J2-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942144#comment-15942144 ] ASF subversion and git services commented on LOG4J2-1856: - Commit 5aff929bb44e63c0dbf0cdc7cfb5d5fbd50660ef in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=5aff929 ] [LOG4J2-1856] Update Jackson from 2.8.6 to 2.8.7. > Update Jackson from 2.8.6 to 2.8.7. > --- > > Key: LOG4J2-1856 > URL: https://issues.apache.org/jira/browse/LOG4J2-1856 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.1 >Reporter: Gary Gregory > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1856) Update Jackson from 2.8.6 to 2.8.7.
[ https://issues.apache.org/jira/browse/LOG4J2-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942143#comment-15942143 ] ASF subversion and git services commented on LOG4J2-1856: - Commit bd16bfe48ecc0fc3119e412f8e8e98398fddf571 in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=bd16bfe ] [LOG4J2-1856] Update Jackson from 2.8.6 to 2.8.7. > Update Jackson from 2.8.6 to 2.8.7. > --- > > Key: LOG4J2-1856 > URL: https://issues.apache.org/jira/browse/LOG4J2-1856 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.8.1 >Reporter: Gary Gregory > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1853) The default value of RandomAccessFileAppender.Builder append field is wrong
[ https://issues.apache.org/jira/browse/LOG4J2-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942126#comment-15942126 ] ASF subversion and git services commented on LOG4J2-1853: - Commit 03e9743e8607f27e6f54d9009404d6c2c5228259 in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=03e9743 ] [LOG4J2-1853] The default value of RandomAccessFileAppender.Builder append field is wrong. > The default value of RandomAccessFileAppender.Builder append field is wrong > --- > > Key: LOG4J2-1853 > URL: https://issues.apache.org/jira/browse/LOG4J2-1853 > Project: Log4j 2 > Issue Type: Bug >Reporter: wangyuntao > Fix For: 2.8.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[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=15931937#comment-15931937 ] ASF subversion and git services commented on LOG4J2-1359: - Commit 311101cb47594a4bc781a5365a471d5be7f40647 in logging-log4j2's branch refs/heads/LOG4J2-1359 from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=311101c ] LOG4J2-1359 - Remove print statement > Add support for Java 9 StackWalker API in ReflectionUtil > > > Key: LOG4J2-1359 > URL: https://issues.apache.org/jira/browse/LOG4J2-1359 > Project: Log4j 2 > Issue Type: Improvement > Components: API > Environment: Java 1.9+ >Reporter: Matt Sicker >Assignee: Ralph Goers > Labels: jdk9 > > [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html] > Based on the functional nature of this API, supporting it may require > compiling at least one class using javac 1.9 and reflectively loading it in > ReflectionUtil similar to how Spring supports newer JDK APIs. > Without support for StackWalker, ReflectionUtil will fall back to using a > slower API in Java 1.9. This is because the Reflection class is a > sun-internal class which are no longer exported to non-JDK code without > setting special command line flags. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[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=15931900#comment-15931900 ] ASF subversion and git services commented on LOG4J2-1359: - Commit 8eac91024cce617b15838c1f630d8aa32703c6f3 in logging-log4j2's branch refs/heads/LOG4J2-1359 from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=8eac910 ] LOG4J2-1359 - Benchmark impact on LogEvent > Add support for Java 9 StackWalker API in ReflectionUtil > > > Key: LOG4J2-1359 > URL: https://issues.apache.org/jira/browse/LOG4J2-1359 > Project: Log4j 2 > Issue Type: Improvement > Components: API > Environment: Java 1.9+ >Reporter: Matt Sicker >Assignee: Ralph Goers > Labels: jdk9 > > [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html] > Based on the functional nature of this API, supporting it may require > compiling at least one class using javac 1.9 and reflectively loading it in > ReflectionUtil similar to how Spring supports newer JDK APIs. > Without support for StackWalker, ReflectionUtil will fall back to using a > slower API in Java 1.9. This is because the Reflection class is a > sun-internal class which are no longer exported to non-JDK code without > setting special command line flags. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[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=15931412#comment-15931412 ] ASF subversion and git services commented on LOG4J2-1359: - Commit e6ce8e4e137f00e9c3ab2f341dfda03c1f76a88a in logging-log4j2's branch refs/heads/LOG4J2-1359 from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=e6ce8e4 ] LOG4J2-1359 - Ignore javadoc problems in core due to Java 9 classes. Modify build instructions > Add support for Java 9 StackWalker API in ReflectionUtil > > > Key: LOG4J2-1359 > URL: https://issues.apache.org/jira/browse/LOG4J2-1359 > Project: Log4j 2 > Issue Type: Improvement > Components: API > Environment: Java 1.9+ >Reporter: Matt Sicker >Assignee: Ralph Goers > Labels: jdk9 > > [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html] > Based on the functional nature of this API, supporting it may require > compiling at least one class using javac 1.9 and reflectively loading it in > ReflectionUtil similar to how Spring supports newer JDK APIs. > Without support for StackWalker, ReflectionUtil will fall back to using a > slower API in Java 1.9. This is because the Reflection class is a > sun-internal class which are no longer exported to non-JDK code without > setting special command line flags. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[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=15931396#comment-15931396 ] ASF subversion and git services commented on LOG4J2-1359: - Commit 4e44466fddb33da1835d82f44a538277741b9156 in logging-log4j2's branch refs/heads/LOG4J2-1359 from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=4e44466 ] LOG4J2-1359 - Remove profiles > Add support for Java 9 StackWalker API in ReflectionUtil > > > Key: LOG4J2-1359 > URL: https://issues.apache.org/jira/browse/LOG4J2-1359 > Project: Log4j 2 > Issue Type: Improvement > Components: API > Environment: Java 1.9+ >Reporter: Matt Sicker >Assignee: Ralph Goers > Labels: jdk9 > > [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html] > Based on the functional nature of this API, supporting it may require > compiling at least one class using javac 1.9 and reflectively loading it in > ReflectionUtil similar to how Spring supports newer JDK APIs. > Without support for StackWalker, ReflectionUtil will fall back to using a > slower API in Java 1.9. This is because the Reflection class is a > sun-internal class which are no longer exported to non-JDK code without > setting special command line flags. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[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=15931099#comment-15931099 ] ASF subversion and git services commented on LOG4J2-1359: - Commit 0854d32523cc2f244a0ed9a927154dadfbf9534e in logging-log4j2's branch refs/heads/LOG4J2-1359 from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=0854d32 ] LOG4J2-1359 - Java 9 support > Add support for Java 9 StackWalker API in ReflectionUtil > > > Key: LOG4J2-1359 > URL: https://issues.apache.org/jira/browse/LOG4J2-1359 > Project: Log4j 2 > Issue Type: Improvement > Components: API > Environment: Java 1.9+ >Reporter: Matt Sicker >Assignee: Ralph Goers > Labels: jdk9 > > [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html] > Based on the functional nature of this API, supporting it may require > compiling at least one class using javac 1.9 and reflectively loading it in > ReflectionUtil similar to how Spring supports newer JDK APIs. > Without support for StackWalker, ReflectionUtil will fall back to using a > slower API in Java 1.9. This is because the Reflection class is a > sun-internal class which are no longer exported to non-JDK code without > setting special command line flags. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module
[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930093#comment-15930093 ] ASF subversion and git services commented on LOG4J2-1851: - Commit 873e7efbab22aac29e29716a871ff114c60202bd in logging-log4j2's branch refs/heads/LOG4J2-1851 from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=873e7ef ] Merge branch 'master' into LOG4J2-1851 > Move org.apache.logging.log4j.core.net.server package to new module > --- > > Key: LOG4J2-1851 > URL: https://issues.apache.org/jira/browse/LOG4J2-1851 > Project: Log4j 2 > Issue Type: Sub-task > Components: Core >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > > Move the SocketServer stuff in org.apache.logging.log4j.core.net.server > package to a new module. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1849) Broken FixedDateFormat tests when daylight saving time starts
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926483#comment-15926483
]
ASF subversion and git services commented on LOG4J2-1849:
-
Commit c822338da47fe6ed5d4377c36ac1153d5621a197 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c822338 ]
LOG4J2-1849 Fixed daylight savings time issue with FixedDateFormat.
> Broken FixedDateFormat tests when daylight saving time starts
> -
>
> Key: LOG4J2-1849
> URL: https://issues.apache.org/jira/browse/LOG4J2-1849
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.8.1
>Reporter: Matt Sicker
>Assignee: Remko Popma
>
> Today we started daylight saving time in the US, and the following tests
> failed:
> {noformat}
> Failed tests:
> FixedDateFormatTest.testFormatLong:162 ABSOLUTE(HH:mm:ss,SSS)/1489305608119
> expected:<0[3]:00:08,119> but was:<0[2]:00:08,119>
> FixedDateFormatTest.testFormatLongCharArrayInt:196
> ABSOLUTE(HH:mm:ss,SSS)/1489305607930 expected:<0[3]:00:07,930> but
> was:<0[2]:00:07,930>
> FixedDateFormatTest.testFormatLongCharArrayInt_goingBackInTime:214
> ABSOLUTE(HH:mm:ss,SSS)/1489381194091 expected:<2[3]:59:54,091> but
> was:<2[2]:59:54,091>
> FixedDateFormatTest.testFormatLong_goingBackInTime:178
> ABSOLUTE(HH:mm:ss,SSS)/1489381194072 expected:<2[3]:59:54,072> but
> was:<2[2]:59:54,072>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1850) Cassendra's integration test fails on Windows
[
https://issues.apache.org/jira/browse/LOG4J2-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906755#comment-15906755
]
ASF subversion and git services commented on LOG4J2-1850:
-
Commit 7091591ae33b9feb3b5531b466e7a825d7df99b1 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=7091591 ]
[LOG4J2-1850]: Fix Cassandra unit tests on Windows
CassandraDaemon attempts to call System.exit() on Windows, so this patch
prevents calls to System.exit() while stopping the daemon.
> Cassendra's integration test fails on Windows
> -
>
> Key: LOG4J2-1850
> URL: https://issues.apache.org/jira/browse/LOG4J2-1850
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.8.2
> Environment: Windows 10
>Reporter: Ludovic HOCHET
>Assignee: Matt Sicker
>Priority: Minor
> Attachments: patch-log4j2-1850.diff
>
>
> While verifying LOG4J2-1753 I tried to clean build the whole Log4J project,
> it failed during the integration tests of the log4j-nosql module with the
> following:
> {quote}
> --- maven-failsafe-plugin:2.19.1:integration-test (integration-tests) @
> log4j-nosql ---
> file.encoding cannot be set as system property, use
> -Dfile.encoding=... instead
> ---
> T E S T S
> ---
> Running org.apache.logging.log4j.nosql.appender.cassandra.CassandraAppenderIT
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 internal initialization logging.
> 23:32:33.958 [Log4j2-TF-1-Cassandra-1] ERROR
> org.apache.cassandra.service.StartupChecks - cassandra.jmx.local.port missing
> from cassandra-env.sh, unable to start local JMX service.
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 internal initialization logging.
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql ---
>
> BUILD FAILURE
>
> Total time: 29.346 s
> Finished at: 2017-03-12T23:32:49+01:00
> Final Memory: 30M/516M
>
> Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (verify) on
> project log4j-nosql: There was a timeout or other error in the fork -> [Help
> 1]
> To see the full stack trace of the errors, re-run Maven with the -e switch.
> Re-run Maven using the -X switch to enable full debug logging.
> For more information about the errors and possible solutions, please read the
> following articles:
> [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1753) java.lang.ClassNotFoundException: org.apache.logging.log4j.core.util.ExecutorServices when running the OSGi tests
[
https://issues.apache.org/jira/browse/LOG4J2-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906675#comment-15906675
]
ASF subversion and git services commented on LOG4J2-1753:
-
Commit 4e1f798ccc2de63054a22f30fa9508bc55139577 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=4e1f798 ]
Add changelog entry for LOG4J2-1753
This was fixed in 2.8.1, but no changelog entry was ever added.
> java.lang.ClassNotFoundException:
> org.apache.logging.log4j.core.util.ExecutorServices when running the OSGi
> tests
> -
>
> Key: LOG4J2-1753
> URL: https://issues.apache.org/jira/browse/LOG4J2-1753
> Project: Log4j 2
> Issue Type: Bug
>Reporter: Ludovic HOCHET
> Fix For: 2.8.1
>
> Attachments: patch-log4j2-1753.diff
>
>
> When running the OSGi tests for LOG4J2-1664, a new
> java.lang.ClassNotFoundException:
> org.apache.logging.log4j.core.util.ExecutorServices (for both Felix and
> Equinox) appeared recently.
> Here is the Felix stack trace:
> {noformat}
> ERROR StatusLogger Failed to preload ExecutorServices class.
> java.lang.ClassNotFoundException: *** Class
> 'org.apache.logging.log4j.core.util.ExecutorServices' was not found because
> bundle org.apache.logging.log4j.api [1] does not import
> 'org.apache.logging.log4j.core.util' even though bundle
> org.apache.logging.log4j.core [2] does export it. To resolve this issue, add
> an import for 'org.apache.logging.log4j.core.util' to bundle
> org.apache.logging.log4j.api [1]. ***
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2011)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.logging.log4j.util.LoaderUtil.loadClass(LoaderUtil.java:141)
> at
> org.apache.logging.log4j.core.LoggerContext.(LoggerContext.java:74)
> at
> org.apache.logging.log4j.core.osgi.BundleContextSelector.locateContext(BundleContextSelector.java:67)
> at
> org.apache.logging.log4j.core.osgi.BundleContextSelector.getContext(BundleContextSelector.java:53)
> at
> org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:57)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:147)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:551)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.logging.log4j.osgi.tests.AbstractLoadBundleTest.log(AbstractLoadBundleTest.java:100)
> at
> org.apache.logging.log4j.osgi.tests.AbstractLoadBundleTest.testSimpleLogInAnOsgiContext(AbstractLoadBundleTest.java:279)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at
[jira] [Commented] (LOG4J2-1848) Add JSON encoding support to EncodingPatternConverter %encode{}.
[
https://issues.apache.org/jira/browse/LOG4J2-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906649#comment-15906649
]
ASF subversion and git services commented on LOG4J2-1848:
-
Commit 07e91be6b1e96fc96709f1a5051c7421ccaa6041 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=07e91be ]
[LOG4J2-1848]: Add JSON encoding support to %enc
This adds an escape format option to EncodingPatternConverter to allow
for either HTML or JSON as the escape format. This converter can be
useful for creating custom JSON layouts via a pattern layout.
> Add JSON encoding support to EncodingPatternConverter %encode{}.
>
>
> Key: LOG4J2-1848
> URL: https://issues.apache.org/jira/browse/LOG4J2-1848
> Project: Log4j 2
> Issue Type: New Feature
> Components: Layouts
>Reporter: Matt Sicker
>Assignee: Matt Sicker
>
> The existing implementation of EncodingPatternConverter is for escaping
> output for HTML specifically. This pattern converter should be extended to
> allow multiple types of encoding. The existing HTML behavior should be the
> default, but an optional second parameter should be added to allow specifying
> a different format to encode for.
> For JSON, encoding would require the following:
> {noformat}
>The representation of strings is similar to conventions used in the C
>family of programming languages. A string begins and ends with
>quotation marks. All Unicode characters may be placed within the
>quotation marks except for the characters that must be escaped:
>quotation mark, reverse solidus, and the control characters (U+
>through U+001F).
>Any character may be escaped. If the character is in the Basic
>Multilingual Plane (U+ through U+), then it may be
>represented as a six-character sequence: a reverse solidus, followed
>by the lowercase letter u, followed by four hexadecimal digits that
>encode the character's code point. The hexadecimal letters A though
>F can be upper or lowercase. So, for example, a string containing
>only a single reverse solidus character may be represented as
>"\u005C".
>Alternatively, there are two-character sequence escape
>representations of some popular characters. So, for example, a
>string containing only a single reverse solidus character may be
>represented more compactly as "\\".
>To escape an extended character that is not in the Basic Multilingual
>Plane, the character is represented as a twelve-character sequence,
>encoding the UTF-16 surrogate pair. So, for example, a string
>containing only the G clef character (U+1D11E) may be represented as
>"\uD834\uDD1E".
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1843) Line-wise common suffix support for %ex pattern
[
https://issues.apache.org/jira/browse/LOG4J2-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906581#comment-15906581
]
ASF subversion and git services commented on LOG4J2-1843:
-
Commit c93c0270e2998f29c033d312192481386e1d4149 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c93c027 ]
Add changelog entry for LOG4J2-1843
> Line-wise common suffix support for %ex pattern
> ---
>
> Key: LOG4J2-1843
> URL: https://issues.apache.org/jira/browse/LOG4J2-1843
> Project: Log4j 2
> Issue Type: New Feature
> Components: Layouts
>Affects Versions: 2.8.1
>Reporter: Zilong Song
>Assignee: Matt Sicker
> Labels: features
> Fix For: 2.8.2
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The [LOG4J2-1838] issue provide us with the feature to print a common suffix
> to each line of a stack trace. But it only implemented the feature for the
> {{%rEx}} and {{%xEx}} pattern, not yet for the {{%ex}} pattern. This issue is
> intended to implement the feature for the {{%ex}} pattern.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1840) Doc issue in example for regex
[
https://issues.apache.org/jira/browse/LOG4J2-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906572#comment-15906572
]
ASF subversion and git services commented on LOG4J2-1840:
-
Commit 1e7dbd57917741a2304e6615f3fc0785bd0efb93 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=1e7dbd5 ]
Add changelog entry for LOG4J2-1840
This closes #65.
> Doc issue in example for regex
> ---
>
> Key: LOG4J2-1840
> URL: https://issues.apache.org/jira/browse/LOG4J2-1840
> Project: Log4j 2
> Issue Type: Documentation
> Components: Documentation
>Reporter: pradeep bala
>Assignee: Matt Sicker
>
> https://logging.apache.org/log4j/log4j-2.3/manual/layouts.html
> replace{pattern}{regex}{substitution}
> has a typo in the example
> "%replace(%msg}{\s}{}"
> fix
> "%replace{%msg}{\s}{}"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1840) Doc issue in example for regex
[
https://issues.apache.org/jira/browse/LOG4J2-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906571#comment-15906571
]
ASF subversion and git services commented on LOG4J2-1840:
-
Commit a04de0b8d8f53ecea8d206940d0ee475fa0e8d88 in logging-log4j2's branch
refs/heads/master from Pradeep Balasundaram
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a04de0b ]
Fixed doc issue LOG4J2-1840
> Doc issue in example for regex
> ---
>
> Key: LOG4J2-1840
> URL: https://issues.apache.org/jira/browse/LOG4J2-1840
> Project: Log4j 2
> Issue Type: Documentation
> Components: Documentation
>Reporter: pradeep bala
>Assignee: Matt Sicker
>
> https://logging.apache.org/log4j/log4j-2.3/manual/layouts.html
> replace{pattern}{regex}{substitution}
> has a typo in the example
> "%replace(%msg}{\s}{}"
> fix
> "%replace{%msg}{\s}{}"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1845) Handle when LogEvent.getLoggerName() returns null in KafkaAppender
[ https://issues.apache.org/jira/browse/LOG4J2-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905077#comment-15905077 ] ASF subversion and git services commented on LOG4J2-1845: - Commit f81faf53eec870810e4e05de9801cdd4f63c in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f81feee ] LOG4J2-1845 Handle when LogEvent.getLoggerName() returns null in KafkaAppender > Handle when LogEvent.getLoggerName() returns null in KafkaAppender > -- > > Key: LOG4J2-1845 > URL: https://issues.apache.org/jira/browse/LOG4J2-1845 > Project: Log4j 2 > Issue Type: Sub-task > Components: Appenders >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1845) Handle when LogEvent.getLoggerName() returns null in KafkaAppender
[ https://issues.apache.org/jira/browse/LOG4J2-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905076#comment-15905076 ] ASF subversion and git services commented on LOG4J2-1845: - Commit e418c39b5a5ebe16d845441c511a5240c4cd55de in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=e418c39 ] LOG4J2-1845 Handle when LogEvent.getLoggerName() returns null in KafkaAppender > Handle when LogEvent.getLoggerName() returns null in KafkaAppender > -- > > Key: LOG4J2-1845 > URL: https://issues.apache.org/jira/browse/LOG4J2-1845 > Project: Log4j 2 > Issue Type: Sub-task > Components: Appenders >Affects Versions: 2.8.1 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1835) Incorrect license info for jeromq at runtime dependencies page
[ https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900681#comment-15900681 ] ASF subversion and git services commented on LOG4J2-1835: - Commit 56d05bcfa908dd76cd500f9efccbf8fc0dc6 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=56d05aa ] [LOG4J2-1835]: Fix docs about JeroMQ licensing Also sorts the changelog a little bit to keep fixes together. > Incorrect license info for jeromq at runtime dependencies page > -- > > Key: LOG4J2-1835 > URL: https://issues.apache.org/jira/browse/LOG4J2-1835 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Affects Versions: 2.8 >Reporter: Konstantin Gribov >Assignee: Matt Sicker >Priority: Minor > Labels: licensing > > Log4j2 runtime deps > [documentation|http://logging.apache.org/log4j/2.x/runtime-dependencies.html] > says that JeroMQ is under LGPL but right before v0.3.6 it was relicensed > under MPL-2.0, see > https://repo1.maven.org/maven2/org/zeromq/jeromq/0.3.6/jeromq-0.3.6.pom and > https://github.com/zeromq/jeromq/issues/327 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace
[
https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900656#comment-15900656
]
ASF subversion and git services commented on LOG4J2-1838:
-
Commit 92310868de5fda62302e2fd9bdd0f73f5464 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=923 ]
[LOG4J2-1838]: Add to changelog
This closes #61.
> Add support for appending common suffix to each line of throwable stack trace
> -
>
> Key: LOG4J2-1838
> URL: https://issues.apache.org/jira/browse/LOG4J2-1838
> Project: Log4j 2
> Issue Type: New Feature
> Components: Pattern Converters
>Affects Versions: 2.8.1
>Reporter: Zilong Song
>Assignee: Matt Sicker
> Labels: features
> Fix For: 2.8.2
>
>
> Add support for appending common suffix to each line of throwable stack
> trace. The suffix can be configured by patterns just like patterns used
> elsewhere.
> For example, pattern {{%xExsuffix(- %mdckey)}} will
> append a string generated by pattern {{-}} and {{%mdckey}}.
> But patterns that handles throwable will be automatically ignored, because
> they will make the rendered result confusing. So pattern {{%xExsuffix(-
> %rEx%mdckey)}} has the same effect with
> {{%xExsuffix(- %mdckey)}}, as if the nested {{%rEx}}
> pattern has never appeared.
> Following is an example of the with such suffix:
> {code:title=stack trace, with pattern "%xExsuffix(-
> %mdckey)" and MDC(key)="test mdc suffix"|borderStyle=solid}
> java.lang.IllegalArgumentException: IllegalArgument - test mdc suffix
> at
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverterTest.testSuffixFromNormalPattern(ExtendedThrowablePatternConverterTest.java:48)
> [test-classes/:?] - test mdc suffix
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_91] - test mdc suffix
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_91] - test mdc suffix
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91] -
> test mdc suffix
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> [idea_rt.jar:?] - test mdc suffix
> Caused by: java.lang.NullPointerException: null pointer - test mdc suffix
> at
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverterTest.testSuffixFromNormalPattern(ExtendedThrowablePatternConverterTest.java:47)
> ~[test-classes/:?] - test mdc suffix
> ... 27 more - test mdc suffix
> }}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1838) Add support for appending common suffix to each line of throwable stack trace
[
https://issues.apache.org/jira/browse/LOG4J2-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900655#comment-15900655
]
ASF subversion and git services commented on LOG4J2-1838:
-
Commit f14eadfb7b49211c282434e5a81ba5b850f7a5bb in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f14eadf ]
[LOG4J2-1838]: Add documentation about throwable suffix() option
Also added notes about related missing documentation.
> Add support for appending common suffix to each line of throwable stack trace
> -
>
> Key: LOG4J2-1838
> URL: https://issues.apache.org/jira/browse/LOG4J2-1838
> Project: Log4j 2
> Issue Type: New Feature
> Components: Pattern Converters
>Affects Versions: 2.8.1
>Reporter: Zilong Song
>Assignee: Matt Sicker
> Labels: features
> Fix For: 2.8.2
>
>
> Add support for appending common suffix to each line of throwable stack
> trace. The suffix can be configured by patterns just like patterns used
> elsewhere.
> For example, pattern {{%xExsuffix(- %mdckey)}} will
> append a string generated by pattern {{-}} and {{%mdckey}}.
> But patterns that handles throwable will be automatically ignored, because
> they will make the rendered result confusing. So pattern {{%xExsuffix(-
> %rEx%mdckey)}} has the same effect with
> {{%xExsuffix(- %mdckey)}}, as if the nested {{%rEx}}
> pattern has never appeared.
> Following is an example of the with such suffix:
> {code:title=stack trace, with pattern "%xExsuffix(-
> %mdckey)" and MDC(key)="test mdc suffix"|borderStyle=solid}
> java.lang.IllegalArgumentException: IllegalArgument - test mdc suffix
> at
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverterTest.testSuffixFromNormalPattern(ExtendedThrowablePatternConverterTest.java:48)
> [test-classes/:?] - test mdc suffix
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_91] - test mdc suffix
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_91] - test mdc suffix
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91] -
> test mdc suffix
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> [idea_rt.jar:?] - test mdc suffix
> Caused by: java.lang.NullPointerException: null pointer - test mdc suffix
> at
> org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverterTest.testSuffixFromNormalPattern(ExtendedThrowablePatternConverterTest.java:47)
> ~[test-classes/:?] - test mdc suffix
> ... 27 more - test mdc suffix
> }}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1839) JdbcAppender.createAppender deprecated
[
https://issues.apache.org/jira/browse/LOG4J2-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898890#comment-15898890
]
ASF subversion and git services commented on LOG4J2-1839:
-
Commit d5b5df4dc9a314a2a48cd14223ac9007b4260273 in logging-log4j2's branch
refs/heads/master from ggregory
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d5b5df4 ]
Refactor existing test before playing with [LOG4J2-1839]
> JdbcAppender.createAppender deprecated
> --
>
> Key: LOG4J2-1839
> URL: https://issues.apache.org/jira/browse/LOG4J2-1839
> Project: Log4j 2
> Issue Type: Improvement
> Components: Appenders
>Affects Versions: 2.8.1
>Reporter: Krzysztof Szymko
> Fix For: 2.8.2
>
>
> As I was migrating 2.7 to 2.8.1 I followed JdbcAppender.newBuilder() API
> to build JDBC appender:
> return JdbcAppender.newBuilder()
> .setBufferSize(bufferSizeInt)
> .setColumnConfigs(columnConfigs)
> .setConnectionSource(connectionSource)
> .setTableName(tableName)
> .withName(name)
> .withIgnoreExceptions(ignoreExceptions)
> .withFilter(filter)
> .build();
> But then I got NPE from JdbcDatabaseManagerFactory @ 275, since
> I did not set any columnMappings. After providing
> .setColumnMappings(columnMappingJDBC)
> to my builder it worked OK. I would suggest to either improve the javadoc or
> add NULL check in JdbcDatabaseManagerFactory.createManager
> as JdbcAppender javadoc says that ColumnMapping is optional:
> This Appender writes logging events to a relational database using standard
> JDBC mechanisms. It takes a list of
> * {@link ColumnConfig}s and/or {@link ColumnMapping}s with
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1836) API Version is incorrect
[ https://issues.apache.org/jira/browse/LOG4J2-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894916#comment-15894916 ] ASF subversion and git services commented on LOG4J2-1836: - Commit 9e7fe9e1a7165b7ffa0d766062e8ec02d34eeadb in logging-log4j2's branch refs/heads/master from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=9e7fe9e ] LOG4J2-1836 - Update the API version > API Version is incorrect > > > Key: LOG4J2-1836 > URL: https://issues.apache.org/jira/browse/LOG4J2-1836 > Project: Log4j 2 > Issue Type: Bug > Components: API, Core >Affects Versions: 2.6, 2.6.1, 2.6.2, 2.7, 2.8, 2.8.1 >Reporter: Ralph Goers > Fix For: 2.8.2 > > > ProviderUtil in Log4j API is supposed to list the versions of the API that > are all compatible with each other from a binding point of view. These > versions are not supposed to be modified with each Log4j release but only > when a change to the API is made so that implementations can know whether > they are compatible with the API. > Likewise, each implemenation (such as Log4j core) is supposed to declare what > version of the API it requires. Again, this is not implemented with each > release but only when core is modified to require changes in the API. > The API changed significantly in releases prior to 2.6 but these values were > never modified. Since 2.6 very little has changed in the API. > To fix this issue the API needs to say the only compatible version is 2.6 and > log4j-core must declare that it requires version 2.6. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1836) API Version is incorrect
[ https://issues.apache.org/jira/browse/LOG4J2-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894911#comment-15894911 ] ASF subversion and git services commented on LOG4J2-1836: - Commit cb25748f18c248d1ae2f38cea6ca894cb45ee527 in logging-log4j2's branch refs/heads/master from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=cb25748 ] LOG4J2-1836 - Update the API version > API Version is incorrect > > > Key: LOG4J2-1836 > URL: https://issues.apache.org/jira/browse/LOG4J2-1836 > Project: Log4j 2 > Issue Type: Bug > Components: API, Core >Affects Versions: 2.6, 2.6.1, 2.6.2, 2.7, 2.8, 2.8.1 >Reporter: Ralph Goers > > ProviderUtil in Log4j API is supposed to list the versions of the API that > are all compatible with each other from a binding point of view. These > versions are not supposed to be modified with each Log4j release but only > when a change to the API is made so that implementations can know whether > they are compatible with the API. > Likewise, each implemenation (such as Log4j core) is supposed to declare what > version of the API it requires. Again, this is not implemented with each > release but only when core is modified to require changes in the API. > The API changed significantly in releases prior to 2.6 but these values were > never modified. Since 2.6 very little has changed in the API. > To fix this issue the API needs to say the only compatible version is 2.6 and > log4j-core must declare that it requires version 2.6. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present
[ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891028#comment-15891028 ] ASF subversion and git services commented on LOG4J2-1820: - Commit 164bb5cc1807cf9c2b847639be8612ab8b50a04b in logging-log4j2's branch refs/heads/master from ggregory [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=164bb5c ] [LOG4J2-1820] Log4j 2.8 can lose exceptions when a security manager is present. > Log4j 2.8 can lose exceptions when a security manager is present > > > Key: LOG4J2-1820 > URL: https://issues.apache.org/jira/browse/LOG4J2-1820 > Project: Log4j 2 > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Jason Tedor > Fix For: 2.8.2 > > Attachments: > 0001-Handle-security-exception-on-getting-class-loader.patch, > 0002-Handle-security-exception-on-getting-class-loader.patch > > > When Log4j is rendering an exception, it can attempt to access a class loader > that it does not have permissions to access when a security manager is > present. > I have a patch and a failing test case for this; I will submit it shortly. > This is similar to LOG4J2-1560. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1831) NullPointerException in HtmlLayout
[
https://issues.apache.org/jira/browse/LOG4J2-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891026#comment-15891026
]
ASF subversion and git services commented on LOG4J2-1831:
-
Commit 9ec88e21312c892c25c01caab42d936d3a299736 in logging-log4j2's branch
refs/heads/master from ggregory
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=9ec88e2 ]
[LOG4J2-1831] NullPointerException in HtmlLayout. Add due-to.
> NullPointerException in HtmlLayout
> --
>
> Key: LOG4J2-1831
> URL: https://issues.apache.org/jira/browse/LOG4J2-1831
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
>Affects Versions: 2.8
>Reporter: Edward Serebrinskiy
>Assignee: Gary Gregory
> Fix For: 2.8.2
>
>
> Got following NullPointerException by using SMTP appender.
> {code}
> AsyncLogger error handling event seq=233, value='[ERROR calling class
> org.apache.logging.log4j.core.async.RingBufferLogEvent.toString():
> java.lang.NullPointerException]':
> org.apache.logging.log4j.core.appender.AppenderLoggingException: An exception
> occurred processing Appender Mail
> at
> org.apache.logging.log4j.core.appender.DefaultErrorHandler.error(DefaultErrorHandler.java:75)
> at
> org.apache.logging.log4j.core.config.AppenderControl.handleAppenderError(AppenderControl.java:165)
> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:158)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:448)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:433)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:417)
> at
> org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:79)
> at
> org.apache.logging.log4j.core.async.AsyncLogger.actualAsyncLog(AsyncLogger.java:337)
> at
> org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:156)
> at
> org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:45)
> at
> org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
> at
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.logging.log4j.LoggingException: Error occurred while
> sending email
> at
> org.apache.logging.log4j.core.net.SmtpManager.sendEvents(SmtpManager.java:175)
> at
> org.apache.logging.log4j.core.appender.SmtpAppender.append(SmtpAppender.java:181)
> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> ... 15 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.logging.log4j.core.layout.HtmlLayout.toSerializable(HtmlLayout.java:170)
> at
> org.apache.logging.log4j.core.layout.HtmlLayout.toSerializable(HtmlLayout.java:50)
> at
> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:301)
> at
> org.apache.logging.log4j.core.net.SmtpManager.writeBuffer(SmtpManager.java:204)
> at
> org.apache.logging.log4j.core.net.SmtpManager.writeContent(SmtpManager.java:190)
> at
> org.apache.logging.log4j.core.net.SmtpManager.formatContentToBytes(SmtpManager.java:182)
> at
> org.apache.logging.log4j.core.net.SmtpManager.sendEvents(SmtpManager.java:163)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1831) NullPointerException in HtmlLayout
[
https://issues.apache.org/jira/browse/LOG4J2-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890873#comment-15890873
]
ASF subversion and git services commented on LOG4J2-1831:
-
Commit c2d7bf0dcf41b5ab6effecc57b627a271f14d470 in logging-log4j2's branch
refs/heads/master from ggregory
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c2d7bf0 ]
[LOG4J2-1831] NullPointerException in HtmlLayout.
> NullPointerException in HtmlLayout
> --
>
> Key: LOG4J2-1831
> URL: https://issues.apache.org/jira/browse/LOG4J2-1831
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
>Affects Versions: 2.8
>Reporter: Edward Serebrinskiy
> Fix For: 2.8.2
>
>
> Got following NullPointerException by using SMTP appender.
> {code}
> AsyncLogger error handling event seq=233, value='[ERROR calling class
> org.apache.logging.log4j.core.async.RingBufferLogEvent.toString():
> java.lang.NullPointerException]':
> org.apache.logging.log4j.core.appender.AppenderLoggingException: An exception
> occurred processing Appender Mail
> at
> org.apache.logging.log4j.core.appender.DefaultErrorHandler.error(DefaultErrorHandler.java:75)
> at
> org.apache.logging.log4j.core.config.AppenderControl.handleAppenderError(AppenderControl.java:165)
> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:158)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:448)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:433)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:417)
> at
> org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:79)
> at
> org.apache.logging.log4j.core.async.AsyncLogger.actualAsyncLog(AsyncLogger.java:337)
> at
> org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:156)
> at
> org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:45)
> at
> org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
> at
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.logging.log4j.LoggingException: Error occurred while
> sending email
> at
> org.apache.logging.log4j.core.net.SmtpManager.sendEvents(SmtpManager.java:175)
> at
> org.apache.logging.log4j.core.appender.SmtpAppender.append(SmtpAppender.java:181)
> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> ... 15 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.logging.log4j.core.layout.HtmlLayout.toSerializable(HtmlLayout.java:170)
> at
> org.apache.logging.log4j.core.layout.HtmlLayout.toSerializable(HtmlLayout.java:50)
> at
> org.apache.logging.log4j.core.layout.AbstractStringLayout.toByteArray(AbstractStringLayout.java:301)
> at
> org.apache.logging.log4j.core.net.SmtpManager.writeBuffer(SmtpManager.java:204)
> at
> org.apache.logging.log4j.core.net.SmtpManager.writeContent(SmtpManager.java:190)
> at
> org.apache.logging.log4j.core.net.SmtpManager.formatContentToBytes(SmtpManager.java:182)
> at
> org.apache.logging.log4j.core.net.SmtpManager.sendEvents(SmtpManager.java:163)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1827) Separate integration tests out of core to speed up build
[ https://issues.apache.org/jira/browse/LOG4J2-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888035#comment-15888035 ] ASF subversion and git services commented on LOG4J2-1827: - Commit 601f06fa3fabf4e130f6bd60659e4b2f4d264786 in logging-log4j2's branch refs/heads/master from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=601f06f ] LOG4J2-1827 - Move integration tests to their own module to speed up build > Separate integration tests out of core to speed up build > > > Key: LOG4J2-1827 > URL: https://issues.apache.org/jira/browse/LOG4J2-1827 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.8 >Reporter: Ralph Goers > Fix For: 2.8.2 > > > The build of the core module experiences a long pause after running the unit > tests while the failsafe plugin looks for integration tests to run. By moving > the integration tests to their own module the pause will be eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1827) Separate integration tests out of core to speed up build
[ https://issues.apache.org/jira/browse/LOG4J2-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888032#comment-15888032 ] ASF subversion and git services commented on LOG4J2-1827: - Commit 87edda8314e290e37ce46fa68ec8964ffd7be200 in logging-log4j2's branch refs/heads/master from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=87edda8 ] LOG4J2-1827 - Move integration tests to their own module to speed up build > Separate integration tests out of core to speed up build > > > Key: LOG4J2-1827 > URL: https://issues.apache.org/jira/browse/LOG4J2-1827 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Affects Versions: 2.8 >Reporter: Ralph Goers > Fix For: 2.8.2 > > > The build of the core module experiences a long pause after running the unit > tests while the failsafe plugin looks for integration tests to run. By moving > the integration tests to their own module the pause will be eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8
[
https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884550#comment-15884550
]
ASF subversion and git services commented on LOG4J2-1804:
-
Commit 88853d4e8406bc4204669ebd295b77c778533293 in logging-log4j2's branch
refs/heads/master from [~ralph_go...@dslextreme.com]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=88853d4 ]
LOG4J2-1804 - Allow %i in file pattern to be preceded with characters other
than just '-'.
> Rolling file %i based rolling broken in 2.8
> ---
>
> Key: LOG4J2-1804
> URL: https://issues.apache.org/jira/browse/LOG4J2-1804
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Brendan Miller
>Assignee: Ralph Goers
> Attachments: LOG4J2-1804.junit.and.fix.patch, LOG4J2-1804.junit.patch
>
>
> Log files do not seem to be rolling up to the max number of files as
> specified in DefaultRolloverStrategy while utilizing a
> SizeBasedTriggeringPolicy. It is just rolling just to 1 file.
> Simple repro:
> log4j2.xml
> {code}
>
>
>
> fileName="__logs__/rolling.log"
> filePattern="__logs__/rolling.log.%i"
> immediateFlush="true">
>
>
>
>
>
>
>
>
>
>
>
> {code}
> MyApp.scala:
> {code}
> import scala.util.Random
> import org.apache.logging.log4j.LogManager
> object MyApp extends App {
> val log = LogManager.getLogger(this.getClass)
> var counter = 0L
> var bytes = new Array[Byte](1000)
> while (true) {
> Random.nextBytes(bytes)
> log.info(f"Log statement: $counter%08x ${bytes.mkString}")
> counter += 1
> Thread.sleep(5)
> }
> }
> {code}
> If you run that against 2.7, things roll fine. If you run that against 2.8,
> you'll only see rolling.log & rolling.log.1 in the __logs__ folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1823) Remove deprecation on MessageSupplier lambda functions in Logger API
[
https://issues.apache.org/jira/browse/LOG4J2-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884050#comment-15884050
]
ASF subversion and git services commented on LOG4J2-1823:
-
Commit 180e7e134aa165d5a43ae6ab04501021907b3bb4 in logging-log4j2's branch
refs/heads/master from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=180e7e1 ]
[LOG4J2-1823]: Remove deprecation on MessageSupplier lambda functions in Logger
API
> Remove deprecation on MessageSupplier lambda functions in Logger API
>
>
> Key: LOG4J2-1823
> URL: https://issues.apache.org/jira/browse/LOG4J2-1823
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
>Affects Versions: 2.6
>Reporter: Matt Sicker
>Assignee: Matt Sicker
> Fix For: 2.8.1
>
>
> The changes done in LOG4J2-1286 to deprecate MessageSupplier were not
> properly tested in practice. Using log4j-api ever since the deprecation, the
> following code causes deprecation warnings:
> {code}
> logger.info(() -> new SimpleMessage("Hello, world!"));
> {code}
> This is because the compiler interprets this as a {{MessageSupplier}} instead
> of the more generic {{Supplier}} version which is the intended API.
> Although manual use of {{MessageSupplier}} should be discouraged, users
> should not have to manually cast the above lambda just to prevent a
> deprecation warning:
> {code}
> logger.info((Supplier) () -> new SimpleMessage("Hello, world!"));
> {code}
> {{MessageSupplier}} should become a normal part of log4j-api with a note on
> both it and {{Supplier}} that these interfaces would be removed in a
> log4j-api 3.0 release and replaced with the Java 8 version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1822) Upgrade SLF4J to version 1.7.24
[ https://issues.apache.org/jira/browse/LOG4J2-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882753#comment-15882753 ] ASF subversion and git services commented on LOG4J2-1822: - Commit a6c3aed0c7a71bd331bacfdf79d409c86851e92c in logging-log4j2's branch refs/heads/master from [~ralph_go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a6c3aed ] LOG4J2-1822 - Update SLF4J to 1.7.24. > Upgrade SLF4J to version 1.7.24 > --- > > Key: LOG4J2-1822 > URL: https://issues.apache.org/jira/browse/LOG4J2-1822 > Project: Log4j 2 > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Ralph Goers >Priority: Minor > Fix For: 2.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1819) Update Jackson from 2.8.5 to 2.8.6
[ https://issues.apache.org/jira/browse/LOG4J2-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872158#comment-15872158 ] ASF subversion and git services commented on LOG4J2-1819: - Commit 8a10178bc0627c7579f936143104efe0a3e296f5 in logging-log4j2's branch refs/heads/master from [~garydgregory] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=8a10178 ] [LOG4J2-1819] Update Jackson from 2.8.5 to 2.8.6. Local build OK (except log4j-nosql which fails on Windows due to the Cassandra code.) > Update Jackson from 2.8.5 to 2.8.6 > -- > > Key: LOG4J2-1819 > URL: https://issues.apache.org/jira/browse/LOG4J2-1819 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.7 >Reporter: Gary Gregory >Assignee: Gary Gregory > > Update Jackson from 2.8.5 to 2.8.6. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()
[
https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871139#comment-15871139
]
ASF subversion and git services commented on LOG4J2-1807:
-
Commit 234ebd46bbe977809f44be380c49ea4d82a9f7eb in logging-log4j2's branch
refs/heads/master from ggregory
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=234ebd4 ]
[LOG4J2-1807][core] Add and implement LogEvent.toImmutable().
> [core] Add and implement LogEvent.toImmutable()
> ---
>
> Key: LOG4J2-1807
> URL: https://issues.apache.org/jira/browse/LOG4J2-1807
> Project: Log4j 2
> Issue Type: New Feature
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Attachments: logging-log4j2.patch
>
>
> [core] Add and implement LogEvent.asImmutable()
> {code:java}
> /**
> * Returns an immutable version of this log event, which MAY BE a copy of
> this event.
> *
> * @return an immutable version of this log event
> */
> LogEvent asImmutable();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()
[
https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871140#comment-15871140
]
ASF subversion and git services commented on LOG4J2-1807:
-
Commit 60cb592e4e7939016eaa6f58a92e3d0648f39d33 in logging-log4j2's branch
refs/heads/master from ggregory
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=60cb592 ]
[LOG4J2-1807][core] Add and implement LogEvent.toImmutable().
> [core] Add and implement LogEvent.toImmutable()
> ---
>
> Key: LOG4J2-1807
> URL: https://issues.apache.org/jira/browse/LOG4J2-1807
> Project: Log4j 2
> Issue Type: New Feature
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Attachments: logging-log4j2.patch
>
>
> [core] Add and implement LogEvent.asImmutable()
> {code:java}
> /**
> * Returns an immutable version of this log event, which MAY BE a copy of
> this event.
> *
> * @return an immutable version of this log event
> */
> LogEvent asImmutable();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1818) Fix rollover to work when filePattern contains no directory components
[
https://issues.apache.org/jira/browse/LOG4J2-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870720#comment-15870720
]
ASF subversion and git services commented on LOG4J2-1818:
-
Commit 62e348b3e44c6328b7b04d69ec7fc5d82950fa34 in logging-log4j2's branch
refs/heads/master from ggregory
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=62e348b ]
[LOG4J2-1818]
Fix rollover to work when filePattern contains no directory components.
> Fix rollover to work when filePattern contains no directory components
> --
>
> Key: LOG4J2-1818
> URL: https://issues.apache.org/jira/browse/LOG4J2-1818
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.8
>Reporter: Gary Gregory
>Assignee: Gary Gregory
>
> See https://github.com/apache/logging-log4j2/pull/59
> Prior to this patch, the following config threw NPE at parent.mkdirs()
> because parent was null when using e.g.:
> {code:xml}
> fileName="foo.log"
> filePattern="foo-%d{-MM-dd}-%i.log.gz"
> immediateFlush="false">
> {code}
> while this config did not:
> {code:xml}
> fileName="foo.log"
> filePattern="./foo-%d{-MM-dd}-%i.log.gz"
> immediateFlush="false">
> {code}
> e.g. by adding ./ in front of the filePattern value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found
[
https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862653#comment-15862653
]
ASF subversion and git services commented on LOG4J2-1812:
-
Commit c826beb94de6912c3bbaa09726235d85aebd5bf5 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c826beb ]
LOG4J2-1812 small grammar fix in error msg
> Improve error message when log4j 2 configuration file not found
> ---
>
> Key: LOG4J2-1812
> URL: https://issues.apache.org/jira/browse/LOG4J2-1812
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
>Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7, 2.8
>Reporter: Remko Popma
>Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> When configuration fails because no Log4j 2 configuration file is found, the
> following message is logged to the console at ERROR level:
> {code}
> No log4j2 configuration file found. Using default configuration: logging only
> errors to the console.
> {code}
> We should be able to improve this. One idea is to add this:
> {code}
> No log4j2 configuration file found. Using default configuration: logging only
> errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 initialization internal logging.
> {code}
> Another idea is to dump the contents of the StatusLogger ring buffer to the
> console.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found
[
https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862651#comment-15862651
]
ASF subversion and git services commented on LOG4J2-1812:
-
Commit 2467ef5af66cbf115bcfda67e23e14821e163b90 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=2467ef5 ]
LOG4J2-1812 Improve error message when log4j 2 configuration file not found
> Improve error message when log4j 2 configuration file not found
> ---
>
> Key: LOG4J2-1812
> URL: https://issues.apache.org/jira/browse/LOG4J2-1812
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
>Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7, 2.8
>Reporter: Remko Popma
>Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> When configuration fails because no Log4j 2 configuration file is found, the
> following message is logged to the console at ERROR level:
> {code}
> No log4j2 configuration file found. Using default configuration: logging only
> errors to the console.
> {code}
> We should be able to improve this. One idea is to add this:
> {code}
> No log4j2 configuration file found. Using default configuration: logging only
> errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 initialization internal logging.
> {code}
> Another idea is to dump the contents of the StatusLogger ring buffer to the
> console.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1810) Upgrade Logback to version 1.2
[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859021#comment-15859021 ] ASF subversion and git services commented on LOG4J2-1810: - Commit 84772ea2189d87a821092977f8eb8d4d936600ee in logging-log4j-boot's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j-boot.git;h=84772ea ] [LOG4J2-1810] Upgrade to Logback 1.2.0 > Upgrade Logback to version 1.2 > -- > > Key: LOG4J2-1810 > URL: https://issues.apache.org/jira/browse/LOG4J2-1810 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.8 >Reporter: Ralph Goers >Priority: Minor > Fix For: boot-1.0-alpha1, 2.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1810) Upgrade Logback to version 1.2
[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859014#comment-15859014 ] ASF subversion and git services commented on LOG4J2-1810: - Commit 311fce5171e9fd197b3f5e35342df173d61c2842 in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=311fce5 ] LOG4J2-1810 - Update to Logback 1.2 > Upgrade Logback to version 1.2 > -- > > Key: LOG4J2-1810 > URL: https://issues.apache.org/jira/browse/LOG4J2-1810 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.8 >Reporter: Ralph Goers >Priority: Minor > Fix For: 2.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1810) Upgrade Logback to version 1.1.10
[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856270#comment-15856270 ] ASF subversion and git services commented on LOG4J2-1810: - Commit 142b5d5e02fffb77aed2e044c9b2d28ab28c638d in logging-log4j2's branch refs/heads/master from [~ralph.go...@dslextreme.com] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=142b5d5 ] LOG4J2-1810 - Update Logback to 1.1.10 > Upgrade Logback to version 1.1.10 > - > > Key: LOG4J2-1810 > URL: https://issues.apache.org/jira/browse/LOG4J2-1810 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.8 >Reporter: Ralph Goers >Priority: Minor > Fix For: 2.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme
[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853311#comment-15853311 ] ASF subversion and git services commented on LOG4J2-1431: - Commit a9bcf176cc154fadae2a464c9743788809cf8ae6 in logging-log4j2's branch refs/heads/LOG4J2-1431 from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a9bcf17 ] [LOG4J2-1809]: Add global configuration environment SPI This adds a PropertySource service provider interface for providing global configuration properties. This also refactors support in LOG4J2-1431 to use these PropertySource providers. > Simplify log4j system property naming scheme > > > Key: LOG4J2-1431 > URL: https://issues.apache.org/jira/browse/LOG4J2-1431 > Project: Log4j 2 > Issue Type: Improvement >Reporter: Matt Sicker >Assignee: Matt Sicker > > As I wonder how to prefix yet another configurable system property, I noticed > we have five families of configuration name prefixes: > log4j.* > log4j2.* > Log4j* > org.apache.logging.log4j.* > > What I'd like to do is strip out all those prefixes and allow any of them, > but change the documentation to use only a single consistent prefix. This > would also make it simpler when writing the properties into a > log4j2.component.properties file as you could omit all the prefixes as they > won't clash with other libraries. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1809) Add global configuration environment SPI
[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853310#comment-15853310 ] ASF subversion and git services commented on LOG4J2-1809: - Commit a9bcf176cc154fadae2a464c9743788809cf8ae6 in logging-log4j2's branch refs/heads/LOG4J2-1431 from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a9bcf17 ] [LOG4J2-1809]: Add global configuration environment SPI This adds a PropertySource service provider interface for providing global configuration properties. This also refactors support in LOG4J2-1431 to use these PropertySource providers. > Add global configuration environment SPI > > > Key: LOG4J2-1809 > URL: https://issues.apache.org/jira/browse/LOG4J2-1809 > Project: Log4j 2 > Issue Type: New Feature > Components: API >Reporter: Matt Sicker >Assignee: Matt Sicker > > Create a service provider interface for global configuration property > sources. Currently, we support two built in sources: properties loaded from a > classpath resource file named "log4j2.component.properties" and from system > properties. This feature will abstract those two sources into an SPI with > default implementations of those two sources as well as environment variables. > This SPI should be specified through the standard > [ServiceLoader|https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html] > API so as to make this simpler to support for users in any environment. > Related to LOG4J2-1431. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme
[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852706#comment-15852706 ] ASF subversion and git services commented on LOG4J2-1431: - Commit bd587cf4e514a62ecd3852e6f1182feeed049fdc in logging-log4j2's branch refs/heads/LOG4J2-1431 from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=bd587cf ] [LOG4J2-1431]: Provide support for simplified global configuration environment This provides the base support for implementing simplified property names along with environment variable support. > Simplify log4j system property naming scheme > > > Key: LOG4J2-1431 > URL: https://issues.apache.org/jira/browse/LOG4J2-1431 > Project: Log4j 2 > Issue Type: Improvement >Reporter: Matt Sicker > > As I wonder how to prefix yet another configurable system property, I noticed > we have five families of configuration name prefixes: > log4j.* > log4j2.* > Log4j* > org.apache.logging.log4j.* > > What I'd like to do is strip out all those prefixes and allow any of them, > but change the documentation to use only a single consistent prefix. This > would also make it simpler when writing the properties into a > log4j2.component.properties file as you could omit all the prefixes as they > won't clash with other libraries. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1756) Adds xmlns in schema and some other tags
[ https://issues.apache.org/jira/browse/LOG4J2-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850233#comment-15850233 ] ASF subversion and git services commented on LOG4J2-1756: - Commit 5b93c1e2fd1e0a0efeb7f74bad84864c714e9f8a in logging-log4j2's branch refs/heads/master from rpopma [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=5b93c1e ] LOG4J2-1756 Commit to close github pull request. This closes #53 > Adds xmlns in schema and some other tags > - > > Key: LOG4J2-1756 > URL: https://issues.apache.org/jira/browse/LOG4J2-1756 > Project: Log4j 2 > Issue Type: Bug > Components: Core >Affects Versions: 2.7 >Reporter: Gary Gregory >Assignee: Gary Gregory > Fix For: 2.8 > > > Adds xmlns in schema and some tags. See > https://github.com/apache/logging-log4j2/pull/53 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1806) Fix javadoc for DefaultRolloverStrategy::purgeAscending
[ https://issues.apache.org/jira/browse/LOG4J2-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850226#comment-15850226 ] ASF subversion and git services commented on LOG4J2-1806: - Commit 12f91ebc700ea7f4a57306a4d84fce2f75f8442b in logging-log4j2's branch refs/heads/master from rpopma [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=12f91eb ] LOG4J2-1806 Fix javadoc for DefaultRolloverStrategy::purgeAscending This closes #41 https://github.com/apache/logging-log4j2/pull/41 > Fix javadoc for DefaultRolloverStrategy::purgeAscending > --- > > Key: LOG4J2-1806 > URL: https://issues.apache.org/jira/browse/LOG4J2-1806 > Project: Log4j 2 > Issue Type: Bug > Components: Documentation >Reporter: Remko Popma >Assignee: Remko Popma > Fix For: 2.8.1 > > > See https://github.com/apache/logging-log4j2/pull/41 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1799) Error determining the current charset
[
https://issues.apache.org/jira/browse/LOG4J2-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850157#comment-15850157
]
ASF subversion and git services commented on LOG4J2-1799:
-
Commit ac51b5bc451f2de2ab80fb42d1b9782c7c785d29 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ac51b5b ]
LOG4J2-1799 Fixed bug in PropertiesUtil::getCharsetProperty that caused
UnsupportedCharsetException for ConsoleAppender.
This closes #57
https://github.com/apache/logging-log4j2/pull/57
> Error determining the current charset
> -
>
> Key: LOG4J2-1799
> URL: https://issues.apache.org/jira/browse/LOG4J2-1799
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Vadim Lotarev
>Assignee: Remko Popma
>Priority: Blocker
>
> Switching to the latest release I've immediately got the following error:
> {code}
> Unable to inject fields into builder class for plugin type class
> org.apache.logging.log4j.core.appender.ConsoleAppender, element Consol
> e. java.nio.charset.UnsupportedCharsetException: sun.stdout.encoding
> {code}
> In the PropertiesUtil I see the following:
> {code:java}
> public Charset getCharsetProperty(final String name, final Charset
> defaultValue) {
> final String prop = getStringProperty(name);
> return prop == null ? defaultValue : Charset.forName(name);
> }
> {code}
> Shouldn't {{prop}} be used in {{Charset.forName(name)}} instead of {{name}}?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1799) Error determining the current charset
[
https://issues.apache.org/jira/browse/LOG4J2-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850156#comment-15850156
]
ASF subversion and git services commented on LOG4J2-1799:
-
Commit e31731b6898a3f241c65fc613e7948284a4a42df in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=e31731b ]
Merge branch 'LOG4J2-1799' of https://github.com/edwgiz/logging-log4j2
> Error determining the current charset
> -
>
> Key: LOG4J2-1799
> URL: https://issues.apache.org/jira/browse/LOG4J2-1799
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Vadim Lotarev
>Assignee: Remko Popma
>Priority: Blocker
>
> Switching to the latest release I've immediately got the following error:
> {code}
> Unable to inject fields into builder class for plugin type class
> org.apache.logging.log4j.core.appender.ConsoleAppender, element Consol
> e. java.nio.charset.UnsupportedCharsetException: sun.stdout.encoding
> {code}
> In the PropertiesUtil I see the following:
> {code:java}
> public Charset getCharsetProperty(final String name, final Charset
> defaultValue) {
> final String prop = getStringProperty(name);
> return prop == null ? defaultValue : Charset.forName(name);
> }
> {code}
> Shouldn't {{prop}} be used in {{Charset.forName(name)}} instead of {{name}}?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1799) Error determining the current charset
[
https://issues.apache.org/jira/browse/LOG4J2-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850155#comment-15850155
]
ASF subversion and git services commented on LOG4J2-1799:
-
Commit 84d816ffbfac090de73ff283307b473850899723 in logging-log4j2's branch
refs/heads/master from [~edwgiz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=84d816f ]
[LOG4J2-1799]: Error determining the current charset
> Error determining the current charset
> -
>
> Key: LOG4J2-1799
> URL: https://issues.apache.org/jira/browse/LOG4J2-1799
> Project: Log4j 2
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Vadim Lotarev
>Assignee: Remko Popma
>Priority: Blocker
>
> Switching to the latest release I've immediately got the following error:
> {code}
> Unable to inject fields into builder class for plugin type class
> org.apache.logging.log4j.core.appender.ConsoleAppender, element Consol
> e. java.nio.charset.UnsupportedCharsetException: sun.stdout.encoding
> {code}
> In the PropertiesUtil I see the following:
> {code:java}
> public Charset getCharsetProperty(final String name, final Charset
> defaultValue) {
> final String prop = getStringProperty(name);
> return prop == null ? defaultValue : Charset.forName(name);
> }
> {code}
> Shouldn't {{prop}} be used in {{Charset.forName(name)}} instead of {{name}}?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1805) FixedDateFormat improvements
[
https://issues.apache.org/jira/browse/LOG4J2-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850111#comment-15850111
]
ASF subversion and git services commented on LOG4J2-1805:
-
Commit d52ce48f74f6abc7f210122788af90a7526bc5ef in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d52ce48 ]
LOG4J2-1805 Fixed rare race condition in FixedDateFormat, made
FixedDateFormat::millisSinceMidnight method public.
> FixedDateFormat improvements
>
>
> Key: LOG4J2-1805
> URL: https://issues.apache.org/jira/browse/LOG4J2-1805
> Project: Log4j 2
> Issue Type: Improvement
> Components: Pattern Converters
>Affects Versions: 2.6
>Reporter: Remko Popma
>Assignee: Remko Popma
> Fix For: 2.8.1
>
>
> *Proposed changes:*
> * improve thread-safety of {{FixedDateFormat::updateMidnightMillis}}
> * expose {{FixedDateFormat::millisSinceMidnight}} as a public method
> In multi-threaded scenarios where time does not move forward monotonically,
> the implementation of {{FixedDateFormat::updateMidnightMillis}} can result in
> corrupted time stamps. In a project I am involved in we have a custom
> PatternConverter that uses FixedDateFormat to format the "event time". In
> these (artificial) tests, event time does not always move forward, so the
> {{updateMidnightMillis}} is called concurrently with varying values. This is
> not a production issue, but the implementation can be improved to be
> thread-safe without impacting performance by using double-checked locking.
> Making {{FixedDateFormat::millisSinceMidnight}} public would provide a
> performant and convenient way to strip off the date component. Useful for
> systems that are on Java 7 or for systems on Java 8 that don't want to
> construct a {{LocalTime}} object every time this value is required.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1803) JMH generated benchmark classes not included in jar
[
https://issues.apache.org/jira/browse/LOG4J2-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850066#comment-15850066
]
ASF subversion and git services commented on LOG4J2-1803:
-
Commit 8ce7dbcdf1d8a92bba3f0c8c9429cd4c8c491306 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=8ce7dbc ]
LOG4J2-1803 changelog
> JMH generated benchmark classes not included in jar
> ---
>
> Key: LOG4J2-1803
> URL: https://issues.apache.org/jira/browse/LOG4J2-1803
> Project: Log4j 2
> Issue Type: Bug
> Components: Core, Performance Benchmarks
>Affects Versions: 2.8
>Reporter: Remko Popma
>Assignee: Ralph Goers
> Fix For: 2.8.1
>
>
> Some time after the 2.7 release, the JMH benchmarks stopped working. When
> trying to execute them, this error occurs:
> {code}
> java.lang.IllegalArgumentException: Benchmark does not match a class
> at org.openjdk.jmh.util.ClassUtils.loadClass(ClassUtils.java:90)
> at org.openjdk.jmh.runner.BaseRunner.runBenchmark(BaseRunner.java:198)
> at org.openjdk.jmh.runner.BaseRunner.runBenchmarks(BaseRunner.java:95)
> at org.openjdk.jmh.runner.ForkedRunner.run(ForkedRunner.java:51)
> at org.openjdk.jmh.runner.ForkedMain.main(ForkedMain.java:68)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.logging.log4j.perf.jmh.generated.FileAppenderBenchmark_julFile
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:195)
> at org.openjdk.jmh.util.ClassUtils.loadClass(ClassUtils.java:72)
> ... 4 more
> {code}
> When I build the project, the classes generated by JMH under
> log4j-perf/target/generated-sources/annotations are not included in the
> shaded benchmarks.jar or in log4j-perf-2.8.1-SNAPSHOT.jar...
> The cause seems to be a change in the master pom:
> the {{maven-compiler-plugin}} plugin now has the below section which was not
> there in 2.7.
> If I take it out and build only log4j-perf, the benchmarks run without error.
> (But building all modules fails: some problem in log4j-core...)
> {code}
>
>
>
> default-compile
>
> compile
>
> compile
>
> none
>
>
>
>
> process-plugins
>
> compile
>
> process-classes
>
> only
>
>
>
> {code}
> From the log4j-dev mailing list:
> {quote}
> That maven-compiler-plugin config was originally only included in log4j-core
> in order to allow the PluginProcessor annotation processor to re-run against
> log4j-core without needing to split it into its own jar. I'm not sure why
> it's configured for everything now.
> {quote}
> Potentially related: somebody reported on StackOverflow that [their custom
> plugin no longer loads with
> 2.8|http://stackoverflow.com/questions/41938128/log4j-2-8-cannot-load-custom-converters-in-osgi-environment].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] (LOG4J2-1802) Convert documentation into Markdown
Title: Message Title ASF subversion and git services commented on LOG4J2-1802 Re: Convert documentation into Markdown Commit 2f0c6064a337fb7e9a6001f6a8648400a51fea25 in logging-log4j2's branch refs/heads/master from Matt Sicker [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=2f0c606 ] LOG4J2-1802: Migrate component sites to markdown Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] [Commented] (LOG4J2-1733) Add SyncSend attribute to KafkaAppender (as in KafkaLog4jAppender)
[ https://issues.apache.org/jira/browse/LOG4J2-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839431#comment-15839431 ] ASF subversion and git services commented on LOG4J2-1733: - Commit 880fcd21484fd2e60bdf607ff4de2f32b2a11bab in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=880fcd2 ] LOG4J2-1733 Caveat in documentation about Kafka syncSend > Add SyncSend attribute to KafkaAppender (as in KafkaLog4jAppender) > -- > > Key: LOG4J2-1733 > URL: https://issues.apache.org/jira/browse/LOG4J2-1733 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.5 > Environment: Kafka 0.10.1.0 >Reporter: Vincent Tieleman >Assignee: Mikael Ståldal > Fix For: 2.8 > > > The KafkaLog4jAppender (shipped with Kafka and usable with log4j), has a > syncsend property that improves performance significantly by not blocking a > send to Kafka. I've tried many other configuration settings and setups, but > find that none of these approaches improved the logging performance to Kafka > as significantly as setting the syncsend property to false. > Unfortunately, the syncsend property is not supported by the KafkaAppender > shipped with log4j2 and the KafkaLog4jAppender only supports log4j, so I am > stuck with forking the code and making the change myself. > Could you please introduce this property in the KafkaAppender in log4j2? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1800) Errors when sending to Kafka with syncSend=false are not reported
[ https://issues.apache.org/jira/browse/LOG4J2-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837485#comment-15837485 ] ASF subversion and git services commented on LOG4J2-1800: - Commit b87f7121833317bf5ea27efc7503760650cb5cb3 in logging-log4j2's branch refs/heads/master from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=b87f712 ] LOG4J2-1800 Report errors when sending to Kafka when using syncSend=false > Errors when sending to Kafka with syncSend=false are not reported > - > > Key: LOG4J2-1800 > URL: https://issues.apache.org/jira/browse/LOG4J2-1800 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.8 >Reporter: Mikael Ståldal >Assignee: Mikael Ståldal > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828646#comment-15828646
]
ASF subversion and git services commented on LOG4J2-1748:
-
Commit 571fb8df680b0db94ad1b6afed478e915b3411a3 in logging-log4j2's branch
refs/heads/master from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=571fb8d ]
LOG4J2-1748 and LOG4J2-1780 Restore interrupted flag on thread
> RollingFile appender prevents a stand alone application to terminate for as
> long as 60 sec
> --
>
> Key: LOG4J2-1748
> URL: https://issues.apache.org/jira/browse/LOG4J2-1748
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.7
> Environment: Java8, Windows
>Reporter: Daniele Demichelis
>Assignee: Mikael Ståldal
> Labels: RollingFile, bug
> Fix For: 2.8
>
>
> This code reproduces what I think is a bug of Log4j2.
> It's a simple loop that logs 2000 messages with two appenders:
> a console appender and a rolling file appender that rolls the file
> every 5Kb. This limit is intentionally low to reproduce what I think is a bug.
> Here's the code.
> {code:java}
> package bug;
>
> import org.apache.logging.log4j.LogManager;
> import org.apache.logging.log4j.Logger;
>
> public class Example {
>
> private static final Logger logger =
> LogManager.getLogger(Example.class);
>
> public static void main(String[] args) throws InterruptedException {
> for(int i = 0; i<2000; i++){
> logger.info("This is log message #{}.", i);
> Thread.sleep(0);
> }
> }
>
> }
> {code}
> Here's the `log4j2.xml` configuration file.
> {code:xml}
>
>
>
>
>
>
> fileName="target/log4j2/roll-by-size/app.log"
>
> filePattern="target/log4j2/roll-by-size/app.%i.log.gz"
> ignoreExceptions="false"
> append="false">
>
> %d{-MM-dd HH:mm:ss} %p %m%n
>
>
>
> size="5 KB"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> What is strange is that when the application is launched you will see this
> logs in the console.
> {code}
> 2016-12-22 22:12:36 INFO This is log message #1993.
> 2016-12-22 22:12:36 INFO This is log message #1994.
> 2016-12-22 22:12:36 INFO This is log message #1995.
> 2016-12-22 22:12:36 INFO This is log message #1996.
> 2016-12-22 22:12:36 INFO This is log message #1997.
> 2016-12-22 22:12:36 INFO This is log message #1998.
> 2016-12-22 22:12:36 INFO This is log message #1999.
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]...
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=StatusLogger]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=ContextSelector]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Loggers,name=bug,
> org.apache.logging.log4j2:type=60199c81,component=Lo
> ggers,name=]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Appenders,name=roll-by-size,
> org.apache.logging.log4j2:type=60199c81,c
> omponent=Appenders,name=stdout]
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncAppenders,name=*'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncLoggerRingBuffer'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=Loggers,name=*,subtype=RingBuffer'
>
[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828649#comment-15828649
]
ASF subversion and git services commented on LOG4J2-1748:
-
Commit d5071900b0c72fccd8bf7e2ccee3a8164d4fdb25 in logging-log4j2's branch
refs/heads/master from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d507190 ]
Merge remote-tracking branch
'origin/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext' into
LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext
> RollingFile appender prevents a stand alone application to terminate for as
> long as 60 sec
> --
>
> Key: LOG4J2-1748
> URL: https://issues.apache.org/jira/browse/LOG4J2-1748
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.7
> Environment: Java8, Windows
>Reporter: Daniele Demichelis
>Assignee: Mikael Ståldal
> Labels: RollingFile, bug
> Fix For: 2.8
>
>
> This code reproduces what I think is a bug of Log4j2.
> It's a simple loop that logs 2000 messages with two appenders:
> a console appender and a rolling file appender that rolls the file
> every 5Kb. This limit is intentionally low to reproduce what I think is a bug.
> Here's the code.
> {code:java}
> package bug;
>
> import org.apache.logging.log4j.LogManager;
> import org.apache.logging.log4j.Logger;
>
> public class Example {
>
> private static final Logger logger =
> LogManager.getLogger(Example.class);
>
> public static void main(String[] args) throws InterruptedException {
> for(int i = 0; i<2000; i++){
> logger.info("This is log message #{}.", i);
> Thread.sleep(0);
> }
> }
>
> }
> {code}
> Here's the `log4j2.xml` configuration file.
> {code:xml}
>
>
>
>
>
>
> fileName="target/log4j2/roll-by-size/app.log"
>
> filePattern="target/log4j2/roll-by-size/app.%i.log.gz"
> ignoreExceptions="false"
> append="false">
>
> %d{-MM-dd HH:mm:ss} %p %m%n
>
>
>
> size="5 KB"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> What is strange is that when the application is launched you will see this
> logs in the console.
> {code}
> 2016-12-22 22:12:36 INFO This is log message #1993.
> 2016-12-22 22:12:36 INFO This is log message #1994.
> 2016-12-22 22:12:36 INFO This is log message #1995.
> 2016-12-22 22:12:36 INFO This is log message #1996.
> 2016-12-22 22:12:36 INFO This is log message #1997.
> 2016-12-22 22:12:36 INFO This is log message #1998.
> 2016-12-22 22:12:36 INFO This is log message #1999.
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]...
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=StatusLogger]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=ContextSelector]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Loggers,name=bug,
> org.apache.logging.log4j2:type=60199c81,component=Lo
> ggers,name=]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Appenders,name=roll-by-size,
> org.apache.logging.log4j2:type=60199c81,c
> omponent=Appenders,name=stdout]
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncAppenders,name=*'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncLoggerRingBuffer'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found
[jira] [Commented] (LOG4J2-1780) Eliminate the use of the ExecutorServices in the LoggerContext
[
https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828647#comment-15828647
]
ASF subversion and git services commented on LOG4J2-1780:
-
Commit 571fb8df680b0db94ad1b6afed478e915b3411a3 in logging-log4j2's branch
refs/heads/master from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=571fb8d ]
LOG4J2-1748 and LOG4J2-1780 Restore interrupted flag on thread
> Eliminate the use of the ExecutorServices in the LoggerContext
> --
>
> Key: LOG4J2-1780
> URL: https://issues.apache.org/jira/browse/LOG4J2-1780
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.7
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.8
>
>
> LoggerContext does not shut down old executor services when creating new ones
> during reconfiguration in {{LoggerContext.setConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828648#comment-15828648
]
ASF subversion and git services commented on LOG4J2-1748:
-
Commit d5071900b0c72fccd8bf7e2ccee3a8164d4fdb25 in logging-log4j2's branch
refs/heads/master from [~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d507190 ]
Merge remote-tracking branch
'origin/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext' into
LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext
> RollingFile appender prevents a stand alone application to terminate for as
> long as 60 sec
> --
>
> Key: LOG4J2-1748
> URL: https://issues.apache.org/jira/browse/LOG4J2-1748
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.7
> Environment: Java8, Windows
>Reporter: Daniele Demichelis
>Assignee: Mikael Ståldal
> Labels: RollingFile, bug
> Fix For: 2.8
>
>
> This code reproduces what I think is a bug of Log4j2.
> It's a simple loop that logs 2000 messages with two appenders:
> a console appender and a rolling file appender that rolls the file
> every 5Kb. This limit is intentionally low to reproduce what I think is a bug.
> Here's the code.
> {code:java}
> package bug;
>
> import org.apache.logging.log4j.LogManager;
> import org.apache.logging.log4j.Logger;
>
> public class Example {
>
> private static final Logger logger =
> LogManager.getLogger(Example.class);
>
> public static void main(String[] args) throws InterruptedException {
> for(int i = 0; i<2000; i++){
> logger.info("This is log message #{}.", i);
> Thread.sleep(0);
> }
> }
>
> }
> {code}
> Here's the `log4j2.xml` configuration file.
> {code:xml}
>
>
>
>
>
>
> fileName="target/log4j2/roll-by-size/app.log"
>
> filePattern="target/log4j2/roll-by-size/app.%i.log.gz"
> ignoreExceptions="false"
> append="false">
>
> %d{-MM-dd HH:mm:ss} %p %m%n
>
>
>
> size="5 KB"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> What is strange is that when the application is launched you will see this
> logs in the console.
> {code}
> 2016-12-22 22:12:36 INFO This is log message #1993.
> 2016-12-22 22:12:36 INFO This is log message #1994.
> 2016-12-22 22:12:36 INFO This is log message #1995.
> 2016-12-22 22:12:36 INFO This is log message #1996.
> 2016-12-22 22:12:36 INFO This is log message #1997.
> 2016-12-22 22:12:36 INFO This is log message #1998.
> 2016-12-22 22:12:36 INFO This is log message #1999.
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]...
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=StatusLogger]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=ContextSelector]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Loggers,name=bug,
> org.apache.logging.log4j2:type=60199c81,component=Lo
> ggers,name=]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Appenders,name=roll-by-size,
> org.apache.logging.log4j2:type=60199c81,c
> omponent=Appenders,name=stdout]
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncAppenders,name=*'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncLoggerRingBuffer'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found
[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828378#comment-15828378
]
ASF subversion and git services commented on LOG4J2-1748:
-
Commit d5071900b0c72fccd8bf7e2ccee3a8164d4fdb25 in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d507190 ]
Merge remote-tracking branch
'origin/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext' into
LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext
> RollingFile appender prevents a stand alone application to terminate for as
> long as 60 sec
> --
>
> Key: LOG4J2-1748
> URL: https://issues.apache.org/jira/browse/LOG4J2-1748
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.7
> Environment: Java8, Windows
>Reporter: Daniele Demichelis
>Assignee: Mikael Ståldal
> Labels: RollingFile, bug
> Fix For: 2.8
>
>
> This code reproduces what I think is a bug of Log4j2.
> It's a simple loop that logs 2000 messages with two appenders:
> a console appender and a rolling file appender that rolls the file
> every 5Kb. This limit is intentionally low to reproduce what I think is a bug.
> Here's the code.
> {code:java}
> package bug;
>
> import org.apache.logging.log4j.LogManager;
> import org.apache.logging.log4j.Logger;
>
> public class Example {
>
> private static final Logger logger =
> LogManager.getLogger(Example.class);
>
> public static void main(String[] args) throws InterruptedException {
> for(int i = 0; i<2000; i++){
> logger.info("This is log message #{}.", i);
> Thread.sleep(0);
> }
> }
>
> }
> {code}
> Here's the `log4j2.xml` configuration file.
> {code:xml}
>
>
>
>
>
>
> fileName="target/log4j2/roll-by-size/app.log"
>
> filePattern="target/log4j2/roll-by-size/app.%i.log.gz"
> ignoreExceptions="false"
> append="false">
>
> %d{-MM-dd HH:mm:ss} %p %m%n
>
>
>
> size="5 KB"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> What is strange is that when the application is launched you will see this
> logs in the console.
> {code}
> 2016-12-22 22:12:36 INFO This is log message #1993.
> 2016-12-22 22:12:36 INFO This is log message #1994.
> 2016-12-22 22:12:36 INFO This is log message #1995.
> 2016-12-22 22:12:36 INFO This is log message #1996.
> 2016-12-22 22:12:36 INFO This is log message #1997.
> 2016-12-22 22:12:36 INFO This is log message #1998.
> 2016-12-22 22:12:36 INFO This is log message #1999.
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]...
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=StatusLogger]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=ContextSelector]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Loggers,name=bug,
> org.apache.logging.log4j2:type=60199c81,component=Lo
> ggers,name=]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Appenders,name=roll-by-size,
> org.apache.logging.log4j2:type=60199c81,c
> omponent=Appenders,name=stdout]
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncAppenders,name=*'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncLoggerRingBuffer'
> 2016-12-22 22:13:36,382
[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828375#comment-15828375
]
ASF subversion and git services commented on LOG4J2-1748:
-
Commit 571fb8df680b0db94ad1b6afed478e915b3411a3 in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=571fb8d ]
LOG4J2-1748 and LOG4J2-1780 Restore interrupted flag on thread
> RollingFile appender prevents a stand alone application to terminate for as
> long as 60 sec
> --
>
> Key: LOG4J2-1748
> URL: https://issues.apache.org/jira/browse/LOG4J2-1748
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.7
> Environment: Java8, Windows
>Reporter: Daniele Demichelis
>Assignee: Mikael Ståldal
> Labels: RollingFile, bug
> Fix For: 2.8
>
>
> This code reproduces what I think is a bug of Log4j2.
> It's a simple loop that logs 2000 messages with two appenders:
> a console appender and a rolling file appender that rolls the file
> every 5Kb. This limit is intentionally low to reproduce what I think is a bug.
> Here's the code.
> {code:java}
> package bug;
>
> import org.apache.logging.log4j.LogManager;
> import org.apache.logging.log4j.Logger;
>
> public class Example {
>
> private static final Logger logger =
> LogManager.getLogger(Example.class);
>
> public static void main(String[] args) throws InterruptedException {
> for(int i = 0; i<2000; i++){
> logger.info("This is log message #{}.", i);
> Thread.sleep(0);
> }
> }
>
> }
> {code}
> Here's the `log4j2.xml` configuration file.
> {code:xml}
>
>
>
>
>
>
> fileName="target/log4j2/roll-by-size/app.log"
>
> filePattern="target/log4j2/roll-by-size/app.%i.log.gz"
> ignoreExceptions="false"
> append="false">
>
> %d{-MM-dd HH:mm:ss} %p %m%n
>
>
>
> size="5 KB"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> What is strange is that when the application is launched you will see this
> logs in the console.
> {code}
> 2016-12-22 22:12:36 INFO This is log message #1993.
> 2016-12-22 22:12:36 INFO This is log message #1994.
> 2016-12-22 22:12:36 INFO This is log message #1995.
> 2016-12-22 22:12:36 INFO This is log message #1996.
> 2016-12-22 22:12:36 INFO This is log message #1997.
> 2016-12-22 22:12:36 INFO This is log message #1998.
> 2016-12-22 22:12:36 INFO This is log message #1999.
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]...
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=StatusLogger]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=ContextSelector]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Loggers,name=bug,
> org.apache.logging.log4j2:type=60199c81,component=Lo
> ggers,name=]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Appenders,name=roll-by-size,
> org.apache.logging.log4j2:type=60199c81,c
> omponent=Appenders,name=stdout]
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncAppenders,name=*'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncLoggerRingBuffer'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
>
[jira] [Commented] (LOG4J2-1780) Eliminate the use of the ExecutorServices in the LoggerContext
[
https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828376#comment-15828376
]
ASF subversion and git services commented on LOG4J2-1780:
-
Commit 571fb8df680b0db94ad1b6afed478e915b3411a3 in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=571fb8d ]
LOG4J2-1748 and LOG4J2-1780 Restore interrupted flag on thread
> Eliminate the use of the ExecutorServices in the LoggerContext
> --
>
> Key: LOG4J2-1780
> URL: https://issues.apache.org/jira/browse/LOG4J2-1780
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.7
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
> Fix For: 2.8
>
>
> LoggerContext does not shut down old executor services when creating new ones
> during reconfiguration in {{LoggerContext.setConfiguration}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828377#comment-15828377
]
ASF subversion and git services commented on LOG4J2-1748:
-
Commit d5071900b0c72fccd8bf7e2ccee3a8164d4fdb25 in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d507190 ]
Merge remote-tracking branch
'origin/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext' into
LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext
> RollingFile appender prevents a stand alone application to terminate for as
> long as 60 sec
> --
>
> Key: LOG4J2-1748
> URL: https://issues.apache.org/jira/browse/LOG4J2-1748
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.7
> Environment: Java8, Windows
>Reporter: Daniele Demichelis
>Assignee: Mikael Ståldal
> Labels: RollingFile, bug
> Fix For: 2.8
>
>
> This code reproduces what I think is a bug of Log4j2.
> It's a simple loop that logs 2000 messages with two appenders:
> a console appender and a rolling file appender that rolls the file
> every 5Kb. This limit is intentionally low to reproduce what I think is a bug.
> Here's the code.
> {code:java}
> package bug;
>
> import org.apache.logging.log4j.LogManager;
> import org.apache.logging.log4j.Logger;
>
> public class Example {
>
> private static final Logger logger =
> LogManager.getLogger(Example.class);
>
> public static void main(String[] args) throws InterruptedException {
> for(int i = 0; i<2000; i++){
> logger.info("This is log message #{}.", i);
> Thread.sleep(0);
> }
> }
>
> }
> {code}
> Here's the `log4j2.xml` configuration file.
> {code:xml}
>
>
>
>
>
>
> fileName="target/log4j2/roll-by-size/app.log"
>
> filePattern="target/log4j2/roll-by-size/app.%i.log.gz"
> ignoreExceptions="false"
> append="false">
>
> %d{-MM-dd HH:mm:ss} %p %m%n
>
>
>
> size="5 KB"/>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> What is strange is that when the application is launched you will see this
> logs in the console.
> {code}
> 2016-12-22 22:12:36 INFO This is log message #1993.
> 2016-12-22 22:12:36 INFO This is log message #1994.
> 2016-12-22 22:12:36 INFO This is log message #1995.
> 2016-12-22 22:12:36 INFO This is log message #1996.
> 2016-12-22 22:12:36 INFO This is log message #1997.
> 2016-12-22 22:12:36 INFO This is log message #1998.
> 2016-12-22 22:12:36 INFO This is log message #1999.
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]
> 2016-12-22 22:13:36,380 pool-1-thread-1 DEBUG Stopping
> LoggerContext[name=60199c81,
> org.apache.logging.log4j.core.LoggerContext@4597ec68]...
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=StatusLogger]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 1 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=ContextSelector]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Loggers,name=bug,
> org.apache.logging.log4j2:type=60199c81,component=Lo
> ggers,name=]
> 2016-12-22 22:13:36,381 pool-1-thread-1 TRACE Unregistering 2 MBeans:
> [org.apache.logging.log4j2:type=60199c81,component=Appenders,name=roll-by-size,
> org.apache.logging.log4j2:type=60199c81,c
> omponent=Appenders,name=stdout]
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncAppenders,name=*'
> 2016-12-22 22:13:36,382 pool-1-thread-1 TRACE Unregistering but no MBeans
> found matching
> 'org.apache.logging.log4j2:type=60199c81,component=AsyncLoggerRingBuffer'
> 2016-12-22 22:13:36,382
[jira] [Commented] (LOG4J2-1648) Provide ability for users to put non-String values in the ThreadContext
[ https://issues.apache.org/jira/browse/LOG4J2-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826785#comment-15826785 ] ASF subversion and git services commented on LOG4J2-1648: - Commit b886eca883699b0ba07d3ab5fc2416efdbed34bf in logging-log4j2's branch refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from [~mikaelstaldal] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=b886eca ] LOG4J2-1648 ObjectThreadContextMap.putAllValues > Provide ability for users to put non-String values in the ThreadContext > --- > > Key: LOG4J2-1648 > URL: https://issues.apache.org/jira/browse/LOG4J2-1648 > Project: Log4j 2 > Issue Type: Improvement > Components: API >Affects Versions: 2.7 >Reporter: Remko Popma > > I would like to discuss possibilities for an API that allows users to put > Object values in the ThreadContext. > Since 2.7, LogEvents can hold non-String values in their context data, but > the Log4j API only allows users to put String values in the ThreadContext. > Not all ThreadContextMap implementations support Object values. For example, > the default ThreadContextMap implementation only allows Strings, to prevent > memory leaks in web apps. > Users need to configure Log4j to use one of the StringMap-based > ThreadContextMap implementations, but even if they do so there is currently > no API that allows them to actually use this and put arbitrary Objects in the > thread context... How can we make this available? > Some ideas: > # Add methods to the ThreadContext facade that allow getting and putting > Object values, and getting a read-only copy of the StringMap. These methods > throw an UnsupportedOperationException if the underlying ThreadContextMap > implementation does not support the operation. There should also be a method > that returns a boolean signifying whether the implementation supports Object > values. > # Add a separate facade class, say, ObjectThreadContext that provides these > methods > # Other? > Without such an API, there is no clean alternative for users to achieve this. > There is also no extension point that would allow them to leverage existing > Log4j code when they build something custom for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1769) JsonLayout Throwing Exceptions And Producing Broken Logs
[
https://issues.apache.org/jira/browse/LOG4J2-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826780#comment-15826780
]
ASF subversion and git services commented on LOG4J2-1769:
-
Commit b34236d8beb2175ff36074a8cf7a40ca73fae59d in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=b34236d ]
LOG4J2-1769 Make sure that GelfLayout is not affected by the same issue
> JsonLayout Throwing Exceptions And Producing Broken Logs
>
>
> Key: LOG4J2-1769
> URL: https://issues.apache.org/jira/browse/LOG4J2-1769
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
>Affects Versions: 2.7
> Environment: All Platforms
>Reporter: Brandon Goodin
>Assignee: Remko Popma
> Fix For: 2.8
>
> Attachments: JSONLayoutIssuesTest.java, log4j2.xml,
> RequestStatistic.java
>
>
> In a multithreaded environment JsonLayout is throwing exceptions and
> producing fragmented logs. We were able to produce a test that demonstrates
> this. The following exceptions and broken logging are being seen.
> {code:title=IllegalArgumentException}
> 2017-01-06 16:57:59,173 Thread-98 ERROR An exception occurred processing
> Appender stdout java.lang.IllegalArgumentException
> at java.nio.Buffer.position(Buffer.java:244)
> at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:191)
> at
> org.apache.logging.log4j.core.layout.AbstractLayout.writeTo(AbstractLayout.java:179)
> at
> org.apache.logging.log4j.core.layout.AbstractLayout.encode(AbstractLayout.java:160)
> at
> org.apache.logging.log4j.core.layout.AbstractLayout.encode(AbstractLayout.java:36)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:176)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:169)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:160)
> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:447)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:432)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:416)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:402)
> at
> org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:63)
> at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:146)
> at
> org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2091)
> at
> org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:1988)
> at
> org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1960)
> at
> org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:1297)
> at
> org.apache.logging.log4j.JSONLayoutIssuesTest$LoggingThread.run(JSONLayoutIssuesTest.java:54)
> {code}
> {code:title=BufferOverflowException}
> 2017-01-06 16:57:59,194 Thread-99 ERROR An exception occurred processing
> Appender stdout java.nio.BufferOverflowException
> at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:189)
> at
> org.apache.logging.log4j.core.layout.AbstractLayout.writeTo(AbstractLayout.java:179)
> at
> org.apache.logging.log4j.core.layout.AbstractLayout.encode(AbstractLayout.java:160)
> at
> org.apache.logging.log4j.core.layout.AbstractLayout.encode(AbstractLayout.java:36)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:176)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:169)
> at
> org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:160)
> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> at
>
[jira] [Commented] (LOG4J2-1589) Value nesting during property substitution
[
https://issues.apache.org/jira/browse/LOG4J2-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826781#comment-15826781
]
ASF subversion and git services commented on LOG4J2-1589:
-
Commit 2a49f555a4a00bdc5a95c852716595a27a73f61b in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~ralph.go...@dslextreme.com]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=2a49f55 ]
LOG4J2-1589
> Value nesting during property substitution
> --
>
> Key: LOG4J2-1589
> URL: https://issues.apache.org/jira/browse/LOG4J2-1589
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
>Affects Versions: 2.5, 2.7
>Reporter: Dmitriy Neretin
>Priority: Minor
> Labels: StrSubstitutor, defaultVariable
> Fix For: 2.8
>
>
> There is already a good description what "default value nesting" is:
> http://logback.qos.ch/manual/configuration.html#nestedSubst
> It is partially implemented in the log4j but it can still be improved.
> The problem appears if your default value is a variable too.
> *Example:* We have a glassfish project. Our log files must be placed to the
> /application/logfiles directory on the server and if we work
> locally somewhere on our computer in the glassfish root
> /application/logfiles.
> The and will be set as a java system
> variables:
> * : -Dpath.configured.by.provisioning=/some/path/onserver/
> * :
> -Dcom.sun.aas.instanceRoot=/glassfishroot/application/logfiles
> At the moment we must have two log4j2.xml config files with different paths
> and it's not so great. So the target is to have only one config files that
> can handle thwo different paths.
> For example:
> {code:xml}
> ...
>
>
> name="path">${sys:path.configured.by.provisioning:-${sys:com.sun.aas.instanceRoot}}/application/logfiles/application/logfiles
>
>
> ...
> {code}
> If we deploy to the server and the value of path.configured.by.provisioning
> is the directory named 'master' the substitution result of StrSubstitutor is
> 'master}' then. But it works if we set this property as default value!:
> ${sys:com.sun.aas.instanceRoot:-${sys:path.configured.by.provisioning}}
> So the default value will be properly substituted, but not the first
> property. The value of the first property is always: }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1243) Faulty placeholder substitution in config xml
[
https://issues.apache.org/jira/browse/LOG4J2-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826782#comment-15826782
]
ASF subversion and git services commented on LOG4J2-1243:
-
Commit c29526014207b3937b70a91c6572c40b6704262d in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~ralph.go...@dslextreme.com]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c295260 ]
LOG4J2-1243 - Enable substitution in variables
> Faulty placeholder substitution in config xml
> -
>
> Key: LOG4J2-1243
> URL: https://issues.apache.org/jira/browse/LOG4J2-1243
> Project: Log4j 2
> Issue Type: Bug
> Components: Lookups
>Affects Versions: 2.5
> Environment: JDK 8
>Reporter: Veit Guna
>Assignee: Ralph Goers
> Fix For: 2.8
>
>
> I'm using log4j 2.5 in a REST service.
> There I would like to use the placeholder substitution to allow configuration
> of the log location.
> I tried this:
> {code:xml}
>
>
> name="logsPath">${sys:mypapp.logs:-${env:MYAPP_LOGS:-logs}}
>
> {code}
> This seems to work quite well with the exception, if myapp.logs is set, the
> path ends with "}". So if I set the system property "-Dmyapp.logs=foobar" it
> creates the directory "foobar}" and puts the logs into that. For the ENV
> substitution it works. It also works when NO placeholder nesting is
> performed. So I guess the problem has something todo with that.
> See:
> http://mail-archives.apache.org/mod_mbox/logging-log4j-user/201601.mbox/%3CD91F2A5E-92AD-4A94-BA89-CCB7B5F83974%40gmail.com%3E
> Thanks
> Veit
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[jira] [Commented] (LOG4J2-1689) ThreadContext.removeAll() method
[
https://issues.apache.org/jira/browse/LOG4J2-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826783#comment-15826783
]
ASF subversion and git services commented on LOG4J2-1689:
-
Commit 5b6322ae773d181a11e6633d0ec1e113f800012b in logging-log4j2's branch
refs/heads/LOG4J2-1748and1780-remove-ExecutorService-from-LoggerContext from
[~mikaelstaldal]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=5b6322a ]
LOG4J2-1689 Rename to CleanableThreadContextMap
> ThreadContext.removeAll() method
>
>
> Key: LOG4J2-1689
> URL: https://issues.apache.org/jira/browse/LOG4J2-1689
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
>Affects Versions: 2.7
>Reporter: Mikael Ståldal
>Assignee: Mikael Ståldal
>Priority: Minor
> Fix For: 2.8
>
>
> There is a {{putAll(Map)}} in ThreadContext. It would be
> useful to have a {{removeAll(Iterable)}} method as a companion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
