[JAVA-336] Support explicitly named pools for JMX Created: 23/Apr/11  Updated: 04/Jun/11  Resolved: 29/May/11

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

Type: Improvement Priority: Minor - P4
Reporter: Ryan Krebs Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Expanding on the improvement in JAVA-318, it might be useful to allow pools to be explicitly named for the purposes of identifying a specific pool via JMX. For example, if I have two applications in tomcat that connect to the same server with the same options, I currently can see both pools with version 2.5.3, but I don't know which belongs to which application.

It looks like the easiest way to allow an application to label pools would be to add a name field to MongoOptions. This could then be added to the ObjectName generated in DBPortPool.Holder, if a value has been supplied by the application. The hashcode portion of the ObjectName added in 2.5.3 would probably remain regardless of whether the application supplies a name, since there's no guarantee that multiple applications would not inadvertently provide the same name.



 Comments   
Comment by auto [ 29/May/11 ]

Author:

{u'login': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: JAVA-336: pool/mongo description
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/1312fbbe07b869da4bb0ba8a1d362473e47028fc

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