ppkarwasz opened a new issue, #3828: URL: https://github.com/apache/logging-log4j2/issues/3828
### Discussed in https://github.com/apache/logging-log4j2/discussions/3827 <div type='discussions-op-text'> <sup>Originally posted by **RichMacDonald** July 15, 2025</sup> Version 2.24.3 org.apache.logging.log4j.core.appender.db.jdbc.AbstractDriverManagerConnectionSource line 162 has a method ````java LOGGER.debug( "{} acquired connection for '{}': {} ({}{@})", getClass().getSimpleName(), actualConnectionString, connection, connection.getClass().getName(), Integer.toHexString(connection.hashCode())); ```` That eventually causes org.apache.logging.log4j.message.ParameterFormatter line 252 to trigger: ````java STATUS_LOGGER.warn( "found {} argument placeholders, but provided {} for pattern `{}`", analysis.placeholderCount, argCount, pattern); ```` ````text Log4j2-TF-12-AsyncLoggerConfig-8 WARN found 4 argument placeholders, but provided 5 for pattern `{} acquired connection for '{}': {} ({}{@})` ```` In practice, this makes logging to JDBC impractical unless status logging level is set to ERROR. Note that the code is the same in the latest (as of today) release of version 2. Log4j version 3 has refactored the classes so I don't know if the issue persists.</div> -- 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: notifications-unsubscr...@logging.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
