[GitHub] [logging-log4j2] vy opened a new pull request #466: LOG4J2-3020 LOG4J2-3021 Improve Logger javadoc for throwing() and catching().
vy opened a new pull request #466: URL: https://github.com/apache/logging-log4j2/pull/466 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (LOG4J2-3022) AsyncLogger with JDBC Appender PoolingDriver not concurrent
[ https://issues.apache.org/jira/browse/LOG4J2-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Wendelmann updated LOG4J2-3022: -- Attachment: recording_local_docker_mssql_buffer_10_asynclogger_1000_runs_AsyncFO.jfr > AsyncLogger with JDBC Appender PoolingDriver not concurrent > --- > > Key: LOG4J2-3022 > URL: https://issues.apache.org/jira/browse/LOG4J2-3022 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders, Configuration, Core, JDBC >Affects Versions: 2.14.0, 2.13.3 > Environment: OS: Win10 Pro 2004 Build 19041.572 > Java: OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.282-b08, mixed mode) > Processor: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 CPUs), ~2.0GHz > Memory: 32768MB RAM >Reporter: Stefan Wendelmann >Priority: Critical > Attachments: > recording_local_docker_mssql_buffer_10_asynclogger_1000_runs_AsyncFO.jfr > > > I tested out the JDBC Logger with a PoolingDriver on several RDBMS (mysql, > mssql, postgre) over the newest JDBC driver and some older ones. > But all have a common problem, they dont act concurrent. > I tired out the AsyncLogger, Asyc Appender, Failover etc. but nothing it > takes long to log. > Then i tried out the h2 in Mem db and its rly fast like from 5min in other > rdbms to 10 sec in h2 ?! > Our Application creates around 600.000 Log entrys / day, and we want to > improve logging by implementing log4j2 in our bigger project, but this is a > nogo for the application. > > I created a github repo for testing things out, flight-recorded some of the > runs here: > [stefanwendelmann/Log4j_JDBC_Test > (github.com)|https://github.com/stefanwendelmann/Log4j_JDBC_Test] > I created a Stack Overflow Question here: > [sql server - Concurrency logging to sql DB - threads not running parallel - > Stack > Overflow|https://stackoverflow.com/questions/66027315/concurrency-logging-to-sql-db-threads-not-running-parallel] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LOG4J2-3021) Logger.throwing(Throwable) does not document level it is logging at
[
https://issues.apache.org/jira/browse/LOG4J2-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285694#comment-17285694
]
ASF subversion and git services commented on LOG4J2-3021:
-
Commit ec3ee87f17dacda26b41481f48ddba4fb98cd570 in logging-log4j2's branch
refs/heads/LOG4J2-3020 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=ec3ee87 ]
LOG4J2-3020 LOG4J2-3021 Improve Logger javadoc regarding throwing() and
catching().
> Logger.throwing(Throwable) does not document level it is logging at
> ---
>
> Key: LOG4J2-3021
> URL: https://issues.apache.org/jira/browse/LOG4J2-3021
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 2.14.0
>Reporter: Marcono1234
>Priority: Major
>
> The
> [documentation|https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/Logger.html#throwing-T-]
> of the method {{Logger.throwing(Throwable)}} is not mentioning at which
> level it is logging at.
> It appears {{AbstractLogger}} is logging at level {{ERROR}}, but without it
> being explicitly mentioned, I think expecting it to be logged at {{DEBUG}}
> might also be a reasonable expectation.
> In fact LOG4J2-1003 implements it to log at debug level, and based on what
> the {{throwing}} documentation suggests as use case, {{AbstractLogger}}
> should be logging at debug level:
> {quote}
> {code}
> throw logger.throwing(myException);
> {code}
> {quote}
> Having an exception which is thrown additionally be logged as error will
> result in duplicate error messages in the log file (unless the exception
> handling is broken), one from the {{throwing}} call and a second one from the
> method handling that exception.
> Therefore {{throwing}} should in my opinion only log at {{DEBUG}} level,
> similar to how {{java.util.logging}} is doing it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (LOG4J2-3020) Logger.catching(Throwable) does not document level it is logging at
[
https://issues.apache.org/jira/browse/LOG4J2-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285693#comment-17285693
]
ASF subversion and git services commented on LOG4J2-3020:
-
Commit ec3ee87f17dacda26b41481f48ddba4fb98cd570 in logging-log4j2's branch
refs/heads/LOG4J2-3020 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=ec3ee87 ]
LOG4J2-3020 LOG4J2-3021 Improve Logger javadoc regarding throwing() and
catching().
> Logger.catching(Throwable) does not document level it is logging at
> ---
>
> Key: LOG4J2-3020
> URL: https://issues.apache.org/jira/browse/LOG4J2-3020
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 2.14.0
>Reporter: Marcono1234
>Priority: Major
>
> The
> [documentation|https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/Logger.html#catching-java.lang.Throwable-]
> of the method {{Logger.catching(Throwable)}} is not mentioning at which
> level it is logging at.
> It appears {{AbstractLogger}} is logging at level {{ERROR}}, but without it
> being explicitly mentioned, I think expecting it to be logged at {{DEBUG}}
> might also be a reasonable expectation.
> It would therefore be good to explicitly mention the log level in the
> documentation.
>
> As a side note: Personally I think the use case described by the {{catching}}
> documentation rather sounds like it should be logged at {{DEBUG}}:
> {quote}
> In other cases where simply logging the fact that an exception was swallowed
> somewhere
> {quote}
> To me that sounds like ignoring exceptions such as timeout exceptions and
> retrying an operation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (LOG4J2-3022) AsyncLogger with JDBC Appender PoolingDriver not concurrent
Stefan Wendelmann created LOG4J2-3022: - Summary: AsyncLogger with JDBC Appender PoolingDriver not concurrent Key: LOG4J2-3022 URL: https://issues.apache.org/jira/browse/LOG4J2-3022 Project: Log4j 2 Issue Type: Bug Components: Appenders, Configuration, Core, JDBC Affects Versions: 2.13.3, 2.14.0 Environment: OS: Win10 Pro 2004 Build 19041.572 Java: OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.282-b08, mixed mode) Processor: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 CPUs), ~2.0GHz Memory: 32768MB RAM Reporter: Stefan Wendelmann I tested out the JDBC Logger with a PoolingDriver on several RDBMS (mysql, mssql, postgre) over the newest JDBC driver and some older ones. But all have a common problem, they dont act concurrent. I tired out the AsyncLogger, Asyc Appender, Failover etc. but nothing it takes long to log. Then i tried out the h2 in Mem db and its rly fast like from 5min in other rdbms to 10 sec in h2 ?! Our Application creates around 600.000 Log entrys / day, and we want to improve logging by implementing log4j2 in our bigger project, but this is a nogo for the application. I created a github repo for testing things out, flight-recorded some of the runs here: [stefanwendelmann/Log4j_JDBC_Test (github.com)|https://github.com/stefanwendelmann/Log4j_JDBC_Test] I created a Stack Overflow Question here: [sql server - Concurrency logging to sql DB - threads not running parallel - Stack Overflow|https://stackoverflow.com/questions/66027315/concurrency-logging-to-sql-db-threads-not-running-parallel] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LOG4J2-3018) Rollover log file at midnight not working
[
https://issues.apache.org/jira/browse/LOG4J2-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285558#comment-17285558
]
Rambabu Bikumandla commented on LOG4J2-3018:
Default rout is there in log4j2.xml
> Rollover log file at midnight not working
> -
>
> Key: LOG4J2-3018
> URL: https://issues.apache.org/jira/browse/LOG4J2-3018
> Project: Log4j 2
> Issue Type: Bug
>Reporter: Rambabu Bikumandla
>Priority: Blocker
> Labels: log4j2.xml, routing
> Attachments: gz_onBothOldNewFile.log, log4j2.xml
>
>
> Hi Team,
> I am migrating my project from log4j1.x to log4j2.11.2 version, while
> migration am seeing below issue could you please provide solution on it.
> *Log4j2 version :*
> *log4j-slf4j-impl-2.11.2*
> *log4j-1.2-api-2.11.2*
> *log4j-1.2-core-2.11.2*
> Issue: log files are not roll out every day midnight with new file name, it
> still writing it to old logs for some hours then switching to new logs.
> Below my log4j2.xml config.
>
>
>
>{color:#ff}*fileName="/app/log/Consumer_${date:-MM-dd}.log*{color}"
> *{color:#ff}filePattern="/app/log/Consumer_%d\{-MM-dd}.log{color}*"
> append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
>
>fileName="/app/log/Provider_${date:-MM-dd}.log"
> filePattern="/app/log/Provider_%d\{-MM-dd}.log" append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
> *Sample Logs: consumer_2021-02-08.log - It should contain only Feb-08 but we
> are seeing Feb-09 also*
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.DbRequest - approval
> status of the myno: 125478412 Is ::W
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO com.bi.myapp.consumer.utils.ConsumerHelper -
> conditional status for the myno ::4857154 is :: false
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.Database - Database
> initialized
> [Feb/08/21 18:18:37] INFO com.app.apptest.MyManagement.Database - Database
> initialized
> [Feb/08/21 18:18:38] INFO com.app.apptest.Database.DbTtion - mynoId :123456
> mynoID :45678
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@516c36a0
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@4ee951e2
> [{color:#FF}Feb/08/21 18:18:38{color}] INFO
> com.bi.myapp.restclients.CircuitImpactClient - constructor: Using environment
> Test to get URL info
> ..
> ..
> {color:#FF}[Feb/09/21 12:37:43{color}] INFO com.bi.myapp.util.Client -
> connectToId: Trying to connect to mail server;
> [Feb/09/21 12:37:44] INFO com.bi.myapp.util.Client - connectToId:
> Successfully connected to .
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: There are 0
> messages to be processed
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: Number of
> unread messages still in the
> [Feb/09/21 12:37:45] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor - updateLock invoked at
> 12:37:45 PM GMT took 3 milliseconds to execute.
> [Feb/09/21 12:37:45] INFO com.bi.myapp.scheduler.EmailReaderScheduler -
> ~
> "consumer_2021-02-08.log" [readonly] 6327556L, 273633483C
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (LOG4J2-3018) Rollover log file at midnight not working
[
https://issues.apache.org/jira/browse/LOG4J2-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rambabu Bikumandla updated LOG4J2-3018:
---
Attachment: (was: log4j2.xml)
> Rollover log file at midnight not working
> -
>
> Key: LOG4J2-3018
> URL: https://issues.apache.org/jira/browse/LOG4J2-3018
> Project: Log4j 2
> Issue Type: Bug
>Reporter: Rambabu Bikumandla
>Priority: Blocker
> Labels: log4j2.xml, routing
> Attachments: gz_onBothOldNewFile.log, log4j2.xml
>
>
> Hi Team,
> I am migrating my project from log4j1.x to log4j2.11.2 version, while
> migration am seeing below issue could you please provide solution on it.
> *Log4j2 version :*
> *log4j-slf4j-impl-2.11.2*
> *log4j-1.2-api-2.11.2*
> *log4j-1.2-core-2.11.2*
> Issue: log files are not roll out every day midnight with new file name, it
> still writing it to old logs for some hours then switching to new logs.
> Below my log4j2.xml config.
>
>
>
>{color:#ff}*fileName="/app/log/Consumer_${date:-MM-dd}.log*{color}"
> *{color:#ff}filePattern="/app/log/Consumer_%d\{-MM-dd}.log{color}*"
> append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
>
>fileName="/app/log/Provider_${date:-MM-dd}.log"
> filePattern="/app/log/Provider_%d\{-MM-dd}.log" append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
> *Sample Logs: consumer_2021-02-08.log - It should contain only Feb-08 but we
> are seeing Feb-09 also*
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.DbRequest - approval
> status of the myno: 125478412 Is ::W
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO com.bi.myapp.consumer.utils.ConsumerHelper -
> conditional status for the myno ::4857154 is :: false
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.Database - Database
> initialized
> [Feb/08/21 18:18:37] INFO com.app.apptest.MyManagement.Database - Database
> initialized
> [Feb/08/21 18:18:38] INFO com.app.apptest.Database.DbTtion - mynoId :123456
> mynoID :45678
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@516c36a0
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@4ee951e2
> [{color:#FF}Feb/08/21 18:18:38{color}] INFO
> com.bi.myapp.restclients.CircuitImpactClient - constructor: Using environment
> Test to get URL info
> ..
> ..
> {color:#FF}[Feb/09/21 12:37:43{color}] INFO com.bi.myapp.util.Client -
> connectToId: Trying to connect to mail server;
> [Feb/09/21 12:37:44] INFO com.bi.myapp.util.Client - connectToId:
> Successfully connected to .
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: There are 0
> messages to be processed
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: Number of
> unread messages still in the
> [Feb/09/21 12:37:45] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor - updateLock invoked at
> 12:37:45 PM GMT took 3 milliseconds to execute.
> [Feb/09/21 12:37:45] INFO com.bi.myapp.scheduler.EmailReaderScheduler -
> ~
> "consumer_2021-02-08.log" [readonly] 6327556L, 273633483C
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (LOGCXX-519) Version11 - "INSTALL.TXT" and "vstudio.apt" miss explenation for generating the log4cxx.dll
[ https://issues.apache.org/jira/browse/LOGCXX-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285551#comment-17285551 ] Robert Middleton commented on LOGCXX-519: - Some of the information in the INSTALL file is out of date as you have discovered. The current way to build log4cxx is to use CMake. Modern versions of Visual Studio support CMake projects directly. The information for the 0.11.0 release can be found under [src/site/apt/building/cmake.apt|https://github.com/apache/logging-log4cxx/blob/v0.11.0/src/site/apt/building/cmake.apt], or you can see the latest docs at [src/site/markdown/building/cmake.md|https://github.com/apache/logging-log4cxx/blob/master/src/site/markdown/development/build-cmake.md] which may have more information. The easiest way to build log4cxx on Windows is to use vcpkg; directions are at [src/site/apt/building/vcpkg.apt|https://github.com/apache/logging-log4cxx/blob/v0.11.0/src/site/apt/building/vcpkg.apt] for version 0.11.0. Issue LOGCXX-510 has some more information on how to build with Visual Studio. > Version11 - "INSTALL.TXT" and "vstudio.apt" miss explenation for generating > the log4cxx.dll > --- > > Key: LOGCXX-519 > URL: https://issues.apache.org/jira/browse/LOGCXX-519 > Project: Log4cxx > Issue Type: Bug > Components: Build, Documentation >Affects Versions: 0.11.0 > Environment: IDE: Microsoft Visual Studio Professional 2019 Version > 16.8.4 > C++ Language Standard: Default (ISO C++14 Standard) >Reporter: Brayan Khosravian >Priority: Blocker > Attachments: image-2021-02-16-14-40-30-658.png > > > Hello! > *Introduktion:* > After downloading the > [apache-log4cxx-0.11.0.zip|https://downloads.apache.org/logging/log4cxx/0.11.0/apache-log4cxx-0.11.0.zip] > I realized that the files "INSTALL.txt" and "vsstudio.apt" do not guide > users to build the "log4cxx.dll" using Visual Studio. > *Tooling:* > IDE: Microsoft Visual Studio Professional 2019 Version 16.8.4 > C++ Language Standard: Default (ISO C++14 Standard) > *Explaining the Issue:* > The "INSTALL.txt" which is located in the root directory redirects me to the > file "src/site/apt/building/vstudio.apt". > *1.)* In the chapter +"*Preparation"+ the components > "apr-1.2.11-win32-src.zip" and "apr-util-1.2.10-win32-src.zip" are mentioned. > There are already newer versions available. What are the newer versions used > for or is the "vstudio.apt" just outdated? > *2.)* We should execute the "configure-aprutil.bat" after the "configure.bat" > but there is no "configure-aprutil.bat" in the folder. > *3.)* In the chapter "*Building log4cxx.dll" we should open > "projects/log4cxx.dsw" with Visual Studio. The issue is, that there is not > "projects" folder in this > [apache-log4cxx-0.11.0.zip|https://downloads.apache.org/logging/log4cxx/0.11.0/apache-log4cxx-0.11.0.zip] > . > *4.)* However, I picked the "projects" folder from Version 10 and tried to > open the "projects/log4cxx.dsw" but as a result the "xml" project can not be > loaded. > !image-2021-02-16-14-40-30-658.png! > > Creating a dll of this library should be more user friendly and straight > forward. > I hope my feedback helps to improve the library, its usability and > documentation. > Sincerely > Brayan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [logging-log4cxx] rm5248 merged pull request #52: Log4cxx Qt support
rm5248 merged pull request #52: URL: https://github.com/apache/logging-log4cxx/pull/52 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4cxx] rm5248 merged pull request #51: Old build tools removal
rm5248 merged pull request #51: URL: https://github.com/apache/logging-log4cxx/pull/51 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[CI][UNSTABLE] Logging/log4j/master#218 has test failures
BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/218/ Project: master Date of build: Tue, 16 Feb 2021 20:54:52 + Build duration: 1 hr 12 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2 Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 10 test(s)Name: org.apache.log4j Failed: 0 test(s), Passed: 144 test(s), Skipped: 0 test(s), Total: 144 test(s)Name: org.apache.log4j.bridge Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)Name: org.apache.log4j.config Failed: 0 test(s), Passed: 150 test(s), Skipped: 0 test(s), Total: 150 test(s)Name: org.apache.log4j.layout Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)Name: org.apache.log4j.pattern Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s)Name: org.apache.logging.log4j Failed: 0 test(s), Passed: 470 test(s), Skipped: 4 test(s), Total: 474 test(s)Name: org.apache.logging.log4j.cassandra Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: org.apache.logging.log4j.configuration Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: org.apache.logging.log4j.core Failed: 0 test(s), Passed: 186 test(s), Skipped: 4 test(s), Total: 190 test(s)Name: org.apache.logging.log4j.core.appender Failed: 0 test(s), Passed: 177 test(s), Skipped: 5 test(s), Total: 182 test(s)Name: org.apache.logging.log4j.core.appender.db Failed: 0 test(s), Passed: 26 test(s), Skipped: 0 test(s), Total: 26 test(s)Name: org.apache.logging.log4j.core.appender.nosql Failed: 0 test(s), Passed: 18 test(s), Skipped: 0 test(s), Total: 18 test(s)Name: org.apache.logging.log4j.core.appender.rewrite Failed: 0 test(s), Passed: 14 test(s), Skipped: 0 test(s), Total: 14 test(s)Name: org.apache.logging.log4j.core.appender.rolling Failed: 0 test(s), Passed: 229 test(s), Skipped: 3 test(s), Total: 232 test(s)Name: org.apache.logging.log4j.core.appender.rolling.action Failed: 0 test(s), Passed: 182 test(s), Skipped: 0 test(s), Total: 182 test(s)Name: org.apache.logging.log4j.core.appender.routing Failed: 0 test(s), Passed: 144 test(s), Skipped: 0 test(s), Total: 144 test(s)Name: org.apache.logging.log4j.core.async Failed: 0 test(s), Passed: 152 test(s), Skipped: 0 test(s), Total: 152 test(s)Name: org.apache.logging.log4j.core.config Failed: 1 test(s), Passed: 349 test(s), Skipped: 2 test(s), Total: 352 test(s)Failed: org.apache.logging.log4j.core.config.FileOutputTest.testConfigName: org.apache.logging.log4j.core.config.builder Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: org.apache.logging.log4j.core.config.plugins Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: org.apache.logging.log4j.core.config.plugins.convert Failed: 0 test(s), Passed: 214 test(s), Skipped: 0 test(s), Total: 214 test(s)Name: org.apache.logging.log4j.core.config.plugins.util Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: org.apache.logging.log4j.core.config.plugins.validation.validators Failed: 0 test(s), Passed: 30 test(s), Skipped: 0 test(s), Total: 30 test(s)Name: org.apache.logging.log4j.core.config.properties Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s)Name: org.apache.logging.log4j.core.config.xml Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: org.apache.logging.log4j.core.filter Failed: 0 test(s), Passed: 100 test(s), Skipped: 0 test(s), Total: 100 test(s)Name: org.apache.logging.log4j.core.impl Failed: 0 test(s), Passed: 308 test(s), Skipped: 0 test(s), Total: 308 test(s)Name: org.apache.logging.log4j.core.jmx Failed: 0 test(s), Passed: 20 test(s), Skipped: 0 test(s), Total: 20 test(s)Name: org.apache.logging.log4j.core.layout Failed: 0 test(s), Passed: 164 test(s), Skipped: 0 test(s), Total: 164 test(s)Name: org.apache.logging.log4j.core.lookup Failed: 0 test(s), Passed: 88 test(s), Skipped: 0 test(s), Total: 88 test(s)Name: org.apache.logging.log4j.core.message Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: org.apache.logging.log4j.core.net Failed: 0 test(s), Passed: 6 test(s), Skipped: 4 test(s), Total: 10 test(s)Name: org.apache.logging.log4j.core.net.ssl Failed: 0 test(s), Passed: 62 test(s), Skipped: 2 test(s), Total: 64 test(s)Name: org.apache.logging.log4j.core.pattern Failed: 0 test(s), Passed: 450 test(s), Skipped: 0 test(s), Total: 450 test(s)Name: org.apache.logging.log4j.core.selector Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: org.apache.logging.log4j.core.time Failed: 0 test(s), Passed: 56 test(s), Skipped: 0 test(s), Total: 56 test(s)Name: org.apache.logging.log4j.core.time.internal Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s)Name: org.apache.logging.log4j.core.time.internal.format Failed: 0 test(s), Passed: 694
[jira] [Commented] (LOG4J2-3019) HtmlLayoutTest.testLayoutWithDatePatternFixedFormat test fails on windows
[
https://issues.apache.org/jira/browse/LOG4J2-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285496#comment-17285496
]
Volkan Yazici commented on LOG4J2-3019:
---
Sorry, I am a Windows noob – but a proud one! Could this discrepancy be due to
environment variables? [~LKleeven], would you share a dump of your environment
variables, please? And if possible, would you repeat the test in an _empty_
environment, that is, Windows-equivalent of
{code:bash}
env -i -- ./mvnw test -pl log4j-core -Dtest=HtmlLayoutTest
{code}
in Linux.
> HtmlLayoutTest.testLayoutWithDatePatternFixedFormat test fails on windows
> -
>
> Key: LOG4J2-3019
> URL: https://issues.apache.org/jira/browse/LOG4J2-3019
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
>Affects Versions: 2.14.0
> Environment: OS: Windows 10 Enterprise
> Version: 20H2
> OS Build: 19042.746
> Experience: Windows Feature Experience Pack 120.2212.551.0
> java version "1.8.0_192"
> Java(TM) SE Runtime Environment (build 1.8.0_192-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.192-b12, mixed mode)
>Reporter: Luc Kleeven
>Assignee: Volkan Yazici
>Priority: Minor
>
> When running a './mvnw verify' on the 'release-2.x' branche, last commit id
> '9788f33fc62b3b4012489a603772433d3440e6b0'. The following test fails:
> {code:java}
> [ERROR]
> HtmlLayoutTest.testLayoutWithDatePatternFixedFormat:242->testLayoutWithDatePatternFixedFormat:273
> Incorrect date=02 Nov 2012 21:34:02,123, format=DATE,
> timezone=GMT+8 ==> expected: <02 nov 2012 21:34:02,123> but was:
> <02 Nov 2012 21:34:02,123> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [logging-log4j2] vy commented on pull request #465: Fixing typos in docs.
vy commented on pull request #465: URL: https://github.com/apache/logging-log4j2/pull/465#issuecomment-780115790 Cherry-picked onto `release-2.x` with some extra little effort. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j2] vy merged pull request #465: Fixing typos in docs.
vy merged pull request #465: URL: https://github.com/apache/logging-log4j2/pull/465 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j2] vy commented on pull request #465: Fixing typos in docs.
vy commented on pull request #465: URL: https://github.com/apache/logging-log4j2/pull/465#issuecomment-780111442 Thanks so much @roberttaylor426, appreciated it! I will merge it right away. As @rgoers noted, these changes will not be visible in the website, which is pointing to the documentation built from `release-2.x` branch. I will try cherry-picking these onto `release-2.x` myself. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (LOG4J2-3017) Groovy logging of GString with $ notation is very slow
[
https://issues.apache.org/jira/browse/LOG4J2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285483#comment-17285483
]
Volkan Yazici commented on LOG4J2-3017:
---
[~cliviu], indeed having a custom {{MessageFactory}} should do the trick. For
the delegate you can use {{ParameterizedMessageFactory}}.
For the records, as far as I can conclude from the discussion so far, we (i.e.,
current maintainers of the project) could not come up with a solution that
would address this issue in a hot-fix. {{log4groovy}} is indeed an interesting
idea that could be considered, but a passionate adventure on its own. These
said, there are good news from the Groovy side! I have poked GROOVY-6360 and
they have managed to land a fix within a day! So, even though it is sad to
admit this as a Log4j maintainer, your chances of getting a new Groovy release
where this {{GString}} problem is fixed is higher than getting a new Log4j
release with a workaround for this problem.
> Groovy logging of GString with $ notation is very slow
> --
>
> Key: LOG4J2-3017
> URL: https://issues.apache.org/jira/browse/LOG4J2-3017
> Project: Log4j 2
> Issue Type: Improvement
>Reporter: Liviu Carausu
>Assignee: Volkan Yazici
>Priority: Major
> Attachments: SomeClass.groovy, TestLogging.groovy
>
>
>
> Logging of GString is very slow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (LOG4J2-3017) Groovy logging of GString with $ notation is very slow
[ https://issues.apache.org/jira/browse/LOG4J2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici updated LOG4J2-3017: -- Component/s: Core > Groovy logging of GString with $ notation is very slow > -- > > Key: LOG4J2-3017 > URL: https://issues.apache.org/jira/browse/LOG4J2-3017 > Project: Log4j 2 > Issue Type: Improvement > Components: Core >Reporter: Liviu Carausu >Assignee: Volkan Yazici >Priority: Major > Attachments: SomeClass.groovy, TestLogging.groovy > > > > Logging of GString is very slow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LOG4J2-3018) Rollover log file at midnight not working
[
https://issues.apache.org/jira/browse/LOG4J2-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285279#comment-17285279
]
Ralph Goers commented on LOG4J2-3018:
-
I do not understand.
Feb 16 00:00 Default_2021-02-15.log.gz
is correct. That file was rolled and compressed at midnight as it should have.
Feb 16 00:00 Default_2021-02-16.log.gz
Are you saying this file exists? It should not and I don't see anything in the
log you sent me to indicate that it does. Log4j should be writing to
Default_2021-02-16.log
As for DefaultError, I explained that in my previous comment.
> Rollover log file at midnight not working
> -
>
> Key: LOG4J2-3018
> URL: https://issues.apache.org/jira/browse/LOG4J2-3018
> Project: Log4j 2
> Issue Type: Bug
>Reporter: Rambabu Bikumandla
>Priority: Blocker
> Labels: log4j2.xml, routing
> Attachments: gz_onBothOldNewFile.log, log4j2.xml, log4j2.xml
>
>
> Hi Team,
> I am migrating my project from log4j1.x to log4j2.11.2 version, while
> migration am seeing below issue could you please provide solution on it.
> *Log4j2 version :*
> *log4j-slf4j-impl-2.11.2*
> *log4j-1.2-api-2.11.2*
> *log4j-1.2-core-2.11.2*
> Issue: log files are not roll out every day midnight with new file name, it
> still writing it to old logs for some hours then switching to new logs.
> Below my log4j2.xml config.
>
>
>
>{color:#ff}*fileName="/app/log/Consumer_${date:-MM-dd}.log*{color}"
> *{color:#ff}filePattern="/app/log/Consumer_%d\{-MM-dd}.log{color}*"
> append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
>
>fileName="/app/log/Provider_${date:-MM-dd}.log"
> filePattern="/app/log/Provider_%d\{-MM-dd}.log" append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
> *Sample Logs: consumer_2021-02-08.log - It should contain only Feb-08 but we
> are seeing Feb-09 also*
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.DbRequest - approval
> status of the myno: 125478412 Is ::W
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO com.bi.myapp.consumer.utils.ConsumerHelper -
> conditional status for the myno ::4857154 is :: false
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.Database - Database
> initialized
> [Feb/08/21 18:18:37] INFO com.app.apptest.MyManagement.Database - Database
> initialized
> [Feb/08/21 18:18:38] INFO com.app.apptest.Database.DbTtion - mynoId :123456
> mynoID :45678
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@516c36a0
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@4ee951e2
> [{color:#FF}Feb/08/21 18:18:38{color}] INFO
> com.bi.myapp.restclients.CircuitImpactClient - constructor: Using environment
> Test to get URL info
> ..
> ..
> {color:#FF}[Feb/09/21 12:37:43{color}] INFO com.bi.myapp.util.Client -
> connectToId: Trying to connect to mail server;
> [Feb/09/21 12:37:44] INFO com.bi.myapp.util.Client - connectToId:
> Successfully connected to .
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: There are 0
> messages to be processed
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: Number of
> unread messages still in the
> [Feb/09/21 12:37:45] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor - updateLock invoked at
> 12:37:45 PM GMT took 3 milliseconds to execute.
> [Feb/09/21 12:37:45] INFO com.bi.myapp.scheduler.EmailReaderScheduler -
> ~
> "consumer_2021-02-08.log" [readonly] 6327556L, 273633483C
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (LOG4J2-3018) Rollover log file at midnight not working
[
https://issues.apache.org/jira/browse/LOG4J2-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285268#comment-17285268
]
Rambabu Bikumandla commented on LOG4J2-3018:
Yes I want to guarantee that they start at server startup , so am implementing
as you suggestion.
May I know , how about wrong date and .gz for "Default" log and "DefaultError"
Feb 16 00:00 Default_2021-02-15.log.gz
Feb 16 00:00 Default_2021-02-16.log.gz
> Rollover log file at midnight not working
> -
>
> Key: LOG4J2-3018
> URL: https://issues.apache.org/jira/browse/LOG4J2-3018
> Project: Log4j 2
> Issue Type: Bug
>Reporter: Rambabu Bikumandla
>Priority: Blocker
> Labels: log4j2.xml, routing
> Attachments: gz_onBothOldNewFile.log, log4j2.xml, log4j2.xml
>
>
> Hi Team,
> I am migrating my project from log4j1.x to log4j2.11.2 version, while
> migration am seeing below issue could you please provide solution on it.
> *Log4j2 version :*
> *log4j-slf4j-impl-2.11.2*
> *log4j-1.2-api-2.11.2*
> *log4j-1.2-core-2.11.2*
> Issue: log files are not roll out every day midnight with new file name, it
> still writing it to old logs for some hours then switching to new logs.
> Below my log4j2.xml config.
>
>
>
>{color:#ff}*fileName="/app/log/Consumer_${date:-MM-dd}.log*{color}"
> *{color:#ff}filePattern="/app/log/Consumer_%d\{-MM-dd}.log{color}*"
> append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
>
>fileName="/app/log/Provider_${date:-MM-dd}.log"
> filePattern="/app/log/Provider_%d\{-MM-dd}.log" append="true">
> onMismatch="DENY" />
>
>
>
>
>
>
> *Sample Logs: consumer_2021-02-08.log - It should contain only Feb-08 but we
> are seeing Feb-09 also*
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.DbRequest - approval
> status of the myno: 125478412 Is ::W
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor
> [Feb/08/21 18:18:37] INFO com.bi.myapp.consumer.utils.ConsumerHelper -
> conditional status for the myno ::4857154 is :: false
> [Feb/08/21 18:18:37] INFO com.app.apptest.Database.Database - Database
> initialized
> [Feb/08/21 18:18:37] INFO com.app.apptest.MyManagement.Database - Database
> initialized
> [Feb/08/21 18:18:38] INFO com.app.apptest.Database.DbTtion - mynoId :123456
> mynoID :45678
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@516c36a0
> [Feb/08/21 18:18:38] INFO com.bi.persistent.process.DBProcess - db is
> ::org.apache.db.oracle.DBCommandOracle@4ee951e2
> [{color:#FF}Feb/08/21 18:18:38{color}] INFO
> com.bi.myapp.restclients.CircuitImpactClient - constructor: Using environment
> Test to get URL info
> ..
> ..
> {color:#FF}[Feb/09/21 12:37:43{color}] INFO com.bi.myapp.util.Client -
> connectToId: Trying to connect to mail server;
> [Feb/09/21 12:37:44] INFO com.bi.myapp.util.Client - connectToId:
> Successfully connected to .
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: There are 0
> messages to be processed
> [Feb/09/21 12:37:45] INFO com.bi.myapp.util.Client - readMails: Number of
> unread messages still in the
> [Feb/09/21 12:37:45] INFO
> com.myapp.servicecore.ejb.monitor.AppTestsEJBMonitor - updateLock invoked at
> 12:37:45 PM GMT took 3 milliseconds to execute.
> [Feb/09/21 12:37:45] INFO com.bi.myapp.scheduler.EmailReaderScheduler -
> ~
> "consumer_2021-02-08.log" [readonly] 6327556L, 273633483C
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (LOGCXX-519) Version11 - "INSTALL.TXT" and "vstudio.apt" miss explenation for generating the log4cxx.dll
Brayan Khosravian created LOGCXX-519: Summary: Version11 - "INSTALL.TXT" and "vstudio.apt" miss explenation for generating the log4cxx.dll Key: LOGCXX-519 URL: https://issues.apache.org/jira/browse/LOGCXX-519 Project: Log4cxx Issue Type: Bug Components: Build, Documentation Affects Versions: 0.11.0 Environment: IDE: Microsoft Visual Studio Professional 2019 Version 16.8.4 C++ Language Standard: Default (ISO C++14 Standard) Reporter: Brayan Khosravian Attachments: image-2021-02-16-14-40-30-658.png Hello! *Introduktion:* After downloading the [apache-log4cxx-0.11.0.zip|https://downloads.apache.org/logging/log4cxx/0.11.0/apache-log4cxx-0.11.0.zip] I realized that the files "INSTALL.txt" and "vsstudio.apt" do not guide users to build the "log4cxx.dll" using Visual Studio. *Tooling:* IDE: Microsoft Visual Studio Professional 2019 Version 16.8.4 C++ Language Standard: Default (ISO C++14 Standard) *Explaining the Issue:* The "INSTALL.txt" which is located in the root directory redirects me to the file "src/site/apt/building/vstudio.apt". *1.)* In the chapter +"*Preparation"+ the components "apr-1.2.11-win32-src.zip" and "apr-util-1.2.10-win32-src.zip" are mentioned. There are already newer versions available. What are the newer versions used for or is the "vstudio.apt" just outdated? *2.)* We should execute the "configure-aprutil.bat" after the "configure.bat" but there is no "configure-aprutil.bat" in the folder. *3.)* In the chapter "*Building log4cxx.dll" we should open "projects/log4cxx.dsw" with Visual Studio. The issue is, that there is not "projects" folder in this [apache-log4cxx-0.11.0.zip|https://downloads.apache.org/logging/log4cxx/0.11.0/apache-log4cxx-0.11.0.zip] . *4.)* However, I picked the "projects" folder from Version 10 and tried to open the "projects/log4cxx.dsw" but as a result the "xml" project can not be loaded. !image-2021-02-16-14-40-30-658.png! Creating a dll of this library should be more user friendly and straight forward. I hope my feedback helps to improve the library, its usability and documentation. Sincerely Brayan -- This message was sent by Atlassian Jira (v8.3.4#803005)
