[SQL-1835] The driver disables all logger when connecting Created: 13/Dec/23  Updated: 22/Jan/24  Resolved: 15/Jan/24

Status: Closed
Project: Atlas SQL
Component/s: mongo-jdbc-driver
Affects Version/s: None
Fix Version/s: jdbc-2.1.0

Type: Bug Priority: Major - P3
Reporter: Martin Bajana Assignee: Natacha Bagnard
Resolution: Fixed Votes: 0
Labels: github-issue
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
SQL Engines
Documentation Changes: Needed
Documentation Changes Summary: Include in release note.
We used to override previously set loggers setting from other applications loading our drivers with our own.
We now only set the logging configuration for our driver.
Reviewers:
Jonathan Chemburkar, Oliver Bucaojit

 Description   

https://github.com/mongodb/mongo-jdbc-driver/issues/243



 Comments   
Comment by Cloud GitHub Webhooks [ 11/Jan/24 ]

nbagnard merged a pull request (SQL-1835 The driver disables all logger when connecting) into the following branch:
master: 90a2f9688798036c55dfde2342f1feb2e71ee4d9

Comment by Natacha Bagnard [ 23/Dec/23 ]

MongoDriver reset the log manager configuration with the configuration of the logging.properties from inside our jar. This is problematic for other applications using JUL as their configuration is deleted.
Instead, we can do the configuration for our Filehandler programmatically.

Generated at Wed Feb 07 20:57:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.