[jira] [Created] (LOG4J2-1408) The module log4j-liquibase is missing from BOM POM

Gary Gregory created LOG4J2-1408: Summary: The module log4j-liquibase is missing from BOM POM Key: LOG4J2-1408 URL: https://issues.apache.org/jira/browse/LOG4J2-1408 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313186#comment-15313186 ] Ralph Goers commented on LOG4J2-1407: - So what was the fix? Saying "In Git master" doesn't tell me

[jira] [Commented] (LOG4J2-1406) 2.6 is re-logging prior throwable instead of logging the throwable that is currently passed in by application code

[ https://issues.apache.org/jira/browse/LOG4J2-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312991#comment-15312991 ] Ralph Goers commented on LOG4J2-1406: - Thanks for the patch! This looks like a pretty simple fix and

[jira] [Closed] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1407. Resolution: Fixed In Git master. > Misleading WARN log events from Log4j about message factories

[jira] [Closed] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1180. Resolution: Fixed Fix Version/s: 2.6.1 > Logger cache does not account for message factory

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313044#comment-15313044 ] Gary Gregory commented on LOG4J2-1180: -- See linked ticket. > Logger cache does not account for

[jira] [Commented] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313123#comment-15313123 ] Ralph Goers commented on LOG4J2-1407: - What is misleading about the warning message? > Misleading

[jira] [Closed] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1407. Resolution: Fixed > Misleading WARN log events from Log4j about message factories and unexpected

[jira] [Created] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

Gary Gregory created LOG4J2-1407: Summary: Misleading WARN log events from Log4j about message factories and unexpected formatting Key: LOG4J2-1407 URL: https://issues.apache.org/jira/browse/LOG4J2-1407

[jira] [Created] (LOG4J2-1406) 2.6 is re-logging prior throwable instead of logging the throwable that is currently passed in by application code

Trask Stalnaker created LOG4J2-1406: --- Summary: 2.6 is re-logging prior throwable instead of logging the throwable that is currently passed in by application code Key: LOG4J2-1406 URL:

[jira] [Updated] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1407: - Description: We log misleading WARN log events from Log4j about message factories and

[jira] [Commented] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313194#comment-15313194 ] Gary Gregory commented on LOG4J2-1407: -- I've updated the description for this issue to show the root

[jira] [Commented] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313178#comment-15313178 ] Gary Gregory commented on LOG4J2-1407: -- In my case, there is nothing wrong with the messages being

[jira] [Reopened] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1407: -- > Misleading WARN log events from Log4j about message factories and unexpected > formatting >

[jira] [Closed] (LOG4J2-1408) The module log4j-liquibase is missing from BOM POM

[ https://issues.apache.org/jira/browse/LOG4J2-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1408. Resolution: Fixed In Git master. > The module log4j-liquibase is missing from BOM POM >

[jira] [Updated] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yuedaxia updated LOG4J2-1404: - Environment: Log4j 2.6 slf4j 1.7.13-21 (was: Log4j 2 2.6 slf4j 1.7.13-21) Description:

[jira] [Assigned] (LOG4J2-997) removeFilter() in AbstractFilterable does not remove filter

[ https://issues.apache.org/jira/browse/LOG4J2-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-997: -- Assignee: Ralph Goers > removeFilter() in AbstractFilterable does not remove filter >

[jira] [Commented] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313253#comment-15313253 ] Remko Popma commented on LOG4J2-1407: - See also discussion at the bottom of LOG4J2-1180. We were

[jira] [Assigned] (LOG4J2-1228) Multiple footers written to file on system restart

[ https://issues.apache.org/jira/browse/LOG4J2-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1228: --- Assignee: Ralph Goers > Multiple footers written to file on system restart >

[jira] [Updated] (LOG4J2-1405) 2.6 html format - "" inserted in the middle of when restart tomcat

[ https://issues.apache.org/jira/browse/LOG4J2-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1405: Description: Hello, Updated 2.3 to 2.6. When reload tomcat7, the logfile (html format) not shown

[jira] [Created] (LOG4J2-1409) ArrayIndexOutOfBoundsException in ReusableParameterizedMessage

Shahan created LOG4J2-1409: -- Summary: ArrayIndexOutOfBoundsException in ReusableParameterizedMessage Key: LOG4J2-1409 URL: https://issues.apache.org/jira/browse/LOG4J2-1409 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1406) 2.6 is re-logging prior throwable instead of logging the throwable that is currently passed in by application code

[ https://issues.apache.org/jira/browse/LOG4J2-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313310#comment-15313310 ] Remko Popma commented on LOG4J2-1406: - Thanks for raising this issue! I believe the null check is

[jira] [Commented] (LOG4J2-1406) 2.6 is re-logging prior throwable instead of logging the throwable that is currently passed in by application code

[ https://issues.apache.org/jira/browse/LOG4J2-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313336#comment-15313336 ] Remko Popma commented on LOG4J2-1406: - Would it be possible to add a unit test that fails now but

[jira] [Commented] (LOG4J2-1032) Rollover startegy failing on high load

[ https://issues.apache.org/jira/browse/LOG4J2-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313337#comment-15313337 ] Ralph Goers commented on LOG4J2-1032: - The RenameAction was modified to use java.nio so it can better

Re: Jenkins build became unstable: Log4j 2.x #1990

We really need to debug this. I wish it happened somewhere besides just the Jenkins build. Ralph > On Jun 2, 2016, at 9:07 PM, Matt Sicker wrote: > > Our old friend bz2. > > On 2 June 2016 at 20:13, Apache Jenkins Server

[jira] [Comment Edited] (LOG4J2-1406) 2.6 is re-logging prior throwable instead of logging the throwable that is currently passed in by application code

[ https://issues.apache.org/jira/browse/LOG4J2-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313310#comment-15313310 ] Remko Popma edited comment on LOG4J2-1406 at 6/2/16 11:49 PM: -- Thanks for

[jira] [Commented] (LOG4J2-1228) Multiple footers written to file on system restart

[ https://issues.apache.org/jira/browse/LOG4J2-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313383#comment-15313383 ] Remko Popma commented on LOG4J2-1228: - Is this related to LOG4J2-1405? > Multiple footers written to

Re: Jenkins build became unstable: Log4j 2.x #1990

Our old friend bz2. On 2 June 2016 at 20:13, Apache Jenkins Server wrote: > See > > > - > To unsubscribe, e-mail:

[jira] [Assigned] (LOG4J2-1409) ArrayIndexOutOfBoundsException in ReusableParameterizedMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1409: --- Assignee: Remko Popma > ArrayIndexOutOfBoundsException in ReusableParameterizedMessage >

[jira] [Updated] (LOG4J2-1409) ArrayIndexOutOfBoundsException in ReusableParameterizedMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1409: Description: A specific set of parameterised logging messages produces an Array Index Out of

Jenkins build became unstable: Log4j 2.x #1990

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Closed] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1404. --- > log4j-slf4j-impl 2.6 is warning > > > Key:

[jira] [Resolved] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1404. - Resolution: Duplicate > log4j-slf4j-impl 2.6 is warning > > >

[jira] [Commented] (LOG4J2-1404) log4j-slf4j-impl 2.6 is warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313501#comment-15313501 ] Remko Popma commented on LOG4J2-1404: - Thank you for reporting this! This issue has been fixed in

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311837#comment-15311837 ] Remko Popma commented on LOG4J2-1180: - I think I deliberately did not do this to avoid binary

[jira] [Updated] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1180: - Attachment: LOG4J2-1180-ggregory.patch > Logger cache does not account for message factory >

[jira] [Commented] (LOG4J2-1404) log4j-slf4j-impl 2.6 is slow and warning

[ https://issues.apache.org/jira/browse/LOG4J2-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311820#comment-15311820 ] Remko Popma commented on LOG4J2-1404: - The warning has also been reported in LOG4J2-1180. What do

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311839#comment-15311839 ] Gary Gregory commented on LOG4J2-1180: -- That seems odd. This means that the factories cannot

[jira] [Comment Edited] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311837#comment-15311837 ] Remko Popma edited comment on LOG4J2-1180 at 6/2/16 6:54 AM: - I think I

[jira] [Updated] (LOG4J2-1394) Minor issues with the 2.6 web site

[ https://issues.apache.org/jira/browse/LOG4J2-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1394: Description: (-) Thanks page: IntelliJ logo missing (-) Appenders page, [RandomAccessFile

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311831#comment-15311831 ] Gary Gregory commented on LOG4J2-1180: -- That might be enough to fix the problem but I believe the

[jira] [Updated] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Schumacher updated LOG4J2-1402: -- Component/s: (was: JCL Bridge) >

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311823#comment-15311823 ] Remko Popma commented on LOG4J2-1180: - I believe it may be sufficient to get the original message

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311884#comment-15311884 ] Remko Popma commented on LOG4J2-1180: - Okay. My main concern is to avoid breaking client code. If

Re: Log4j 2.6.1

+1 Sounds reasonable On Thu, Jun 2, 2016 at 3:22 AM, Matt Sicker wrote: > +1 for 2.6.1. Plus, we have website fixes, too. > > On 1 June 2016 at 18:01, Gary Gregory wrote: > >> >> On Jun 1, 2016 2:57 PM, "Ralph Goers" wrote:

[jira] [Comment Edited] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312078#comment-15312078 ] Pascal Schumacher edited comment on LOG4J2-1402 at 6/2/16 10:07 AM:

[jira] [Comment Edited] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312078#comment-15312078 ] Pascal Schumacher edited comment on LOG4J2-1402 at 6/2/16 10:07 AM:

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312083#comment-15312083 ] Pascal Schumacher commented on LOG4J2-1402: --- Thanks you very much. Sorry again for supplying

[jira] [Closed] (LOG4J2-1263) log4j2.properties: monitorInterval has no effect

[ https://issues.apache.org/jira/browse/LOG4J2-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Schumacher closed LOG4J2-1263. - I was able to verify that it works fine with 2.6. Thanks! > log4j2.properties:

[jira] [Commented] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312078#comment-15312078 ] Pascal Schumacher commented on LOG4J2-1402: --- You are correct, there were multiple

[jira] [Updated] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Schumacher updated LOG4J2-1402: -- Summary: Exception when using log4j2.properties and logger with dash (was:

[jira] [Commented] (LOG4J2-1235) org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working correctly

[ https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312071#comment-15312071 ] Sascha Scholz commented on LOG4J2-1235: --- I'm not able to test it in a realistic environment at the

[jira] [Comment Edited] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312083#comment-15312083 ] Pascal Schumacher edited comment on LOG4J2-1402 at 6/2/16 10:14 AM:

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312478#comment-15312478 ] Ralph Goers commented on LOG4J2-1402: - Did you deploy it? Our Jenkins build doesn't deploy the

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312375#comment-15312375 ] Matt Sicker commented on LOG4J2-1402: - Apache snapshots repository:

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312633#comment-15312633 ] Ralph Goers commented on LOG4J2-1402: - My mistake. The build does mvn clean install but there is a

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312626#comment-15312626 ] Matt Sicker commented on LOG4J2-1402: - It looks like it's being deployed, though. I thought that was

[jira] [Issue Comment Deleted] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1402: Comment: was deleted (was: It looks like it's being deployed, though. I thought that was from

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312627#comment-15312627 ] Matt Sicker commented on LOG4J2-1402: - It looks like it's being deployed, though. I thought that was

[jira] [Created] (LOG4J2-1405) 2.6 html format - "" inserted in the middle of when restart tomcat

yl created LOG4J2-1405: -- Summary: 2.6 html format - "" inserted in the middle of when restart tomcat Key: LOG4J2-1405 URL: https://issues.apache.org/jira/browse/LOG4J2-1405 Project: Log4j 2 Issue