Environment
Analytics Database 25.3
Situation
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }
After upgrading from JDBC 23.4.0-0 to 25.3.0-0 (and later to 25.3.0-3), JDBC logs could no longer be combined with application logs. The client runs in a container, and logs are directed to stdout for collection by the Docker log driver. Previously, setting the JDBC DataSource property LogPath to an invalid directory caused the driver to fall back to a default StreamHandler, sending messages to stdout and allowing integration with application logs.
This behavior has changed. The driver now throws a NullPointerException instead of using StreamHandler. Current file-based logging creates numerous files—one per connection. With a Hikari pool of 20 connections and a 30-minute max lifetime, approximately 40 log files are generated per hour, which is unmanageable.
Although JDBC logging is generally disabled, it is used in automated component tests and may need to be enabled at INFO level to meet TLS logging requirements for Common Criteria.
Please advise if there is an alternative method to configure the JDBC driver to use StreamHandler. If not, consider recording a defect or enhancement request to support stream-based logging.
