[JAVA-4189] Change logging of connection closed events from INFO to DEBUG Created: 03/Jun/21  Updated: 28/Oct/23  Resolved: 15/Jun/21

Status: Closed
Project: Java Driver
Component/s: Connection Management, Monitoring
Affects Version/s: None
Fix Version/s: 3.12.9, 4.3.0

Type: Improvement Priority: Unknown
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Documentation Changes: Not Needed

 Description   

It's the only INFO-level logging in the connection pool, and I don't see why it's not DEBUG. It's also causing our CI log files to blow up because of a new-ish concurrency test of the connection pool.



 Comments   
Comment by Githook User [ 15/Jun/21 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Change connection-closed log message to debug

Previously it was info, and it's the only connection pool-related
log message at that high a level.

JAVA-4189
Branch: 3.12.x
https://github.com/mongodb/mongo-java-driver/commit/42193595f35af4c7c9270a0c7ca3cb74092bb858

Comment by Githook User [ 15/Jun/21 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Change connection-closed log message to debug (#728)

Previously it was info, and it's the only connection pool-related
log message at that high a level.

JAVA-4189
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/11f2fcb576863b14b954b9f1bf045e855428be5f

Generated at Thu Feb 08 09:01:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.