[LOG4J2-3022] AsyncLogger with JDBC Appender PoolingDriver not concurrent

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.14.0, 2.13.3
• Component/s: Appenders, Configuration, Core, JDBC

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

• Assignee: Unassigned
• Reporter: Stefan Wendelmann
• Created: 17/Feb/21 07:55
• Updated: 18/Jan/22 12:31

Description

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:file db and its rly fast like from 40min 30 sec in other rdbms to 20 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)

I created a Stack Overflow Question here:

sql server - Concurrency logging to sql DB - threads not running parallel - Stack Overflow