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)
