[JAVA-1583] Disable JMX registration Created: 03/Dec/14  Updated: 06/Apr/23  Resolved: 08/Nov/17

Status: Closed
Project: Java Driver
Component/s: Monitoring
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Arsene Costin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to JAVA-805 Make connection pool and connection s... Closed

 Description   

It will be nice If you could disable JMX registration on Mongo.
In our context we have several wars inside Tomcat that uses the same Mongodb database.
Upon loading the driver register to the same Mbean and we might get some issues here.



 Comments   
Comment by Jeffrey Yemin [ 08/Nov/17 ]

As part of JAVA-805 the driver no longer registers a connection pool MBean by default. Applications that want it can configure it manually via MongoClientOptions.Builder.addConnectionPoolListener.

Comment by Arsene Costin [ 04/Dec/14 ]

I understand that but for us it will be nice if we do not have any JMX registration.

Comment by Jeffrey Yemin [ 03/Dec/14 ]

Note that in 3.0 the duplicate registration issue is resolved, as an ObjectId is used to provide uniqueness even in the face of multiple class loaders.

Generated at Thu Feb 08 08:54:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.