[JAVA-2662] Document that JMXConnectionPoolListener is no longer registered by default Created: 14/Nov/17 Updated: 29/Oct/23 Resolved: 02/Feb/18 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Documentation |
| Affects Version/s: | 3.5.0 |
| Fix Version/s: | 3.6.2 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Danny Shemesh | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | jmx, mxbean | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Description |
|
Hey ! We've noticed that JMXConnectionPoolListener is not instantiated or used since version 3.5.0 - which means that the mxbean isn't registered automatically. I was wondering if that's intentional - and if so, if you could please update the docs to mention this. Thanks a lot,
|
| Comments |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'jeff.yemin@10gen.com', 'name': 'Jeff Yemin', 'username': 'jyemin'}Message: |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'jeff.yemin@10gen.com', 'name': 'Jeff Yemin', 'username': 'jyemin'}Message: |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'jeff.yemin@10gen.com', 'name': 'Jeff Yemin', 'username': 'jyemin'}Message: |
| Comment by Ross Lawley [ 14/Nov/17 ] |
|
Hi dashemes, In 3.5.0 we added a formalized way of handling connection pool monitoring. The JMXConnectionPoolListener went from being a Beta class to now being officially supported. The changes made by the formalized command monitoring specification meant that custom Connection Pool listeners can also be applied. The API changes meant configuring custom listener configurations is now simplified and the need for a default is reduced. I'll look to update the upgrading page to make a note that it now needs to be explicitly configured. Thanks again for bringing this to our attention. Ross |