Support explicitly named pools for JMX

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Minor - P4
    • 2.6.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Scott Hernandez (Inactive)
              Reporter:
              Ryan Krebs
              None
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: