ppkarwasz opened a new issue, #1916: URL: https://github.com/apache/logging-log4j2/issues/1916
The JDBC appender takes a very conservative approach to SQL connection sharing: 1. as most appenders, each `append` call is synchronized, 2. each event (or batch of events) is logged using a different `Connection` object, which is closed at the end of the call, 3. to prevent the high performance hit from creating many `Connection`s, users are advised to use a connection pool like DBCP2. This approach has many disadvantages: - it does not profit from the connection pool, since at any time at **most** one connection will be borrowed from the pool, - on the other hand users that use `DriverManager` get a performance hit, even if 1. ensures that no `Connection` object will be used concurrently on multiple threads. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
