[
https://jira.jboss.org/jira/browse/TEIID-580?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-580.
----------------------------------
Resolution: Done
Changed the embedded logic to ensure mmconnectionpools were being returned to the client.
I'm not sure what we'll need for additional documentation here, since we currently
consider JavaDoc the doc source for AdminApi.
Add ability to monitor Connector Connection Pool
-------------------------------------------------
Key: TEIID-580
URL:
https://jira.jboss.org/jira/browse/TEIID-580
Project: Teiid
Issue Type: Feature Request
Components: AdminApi, Query Engine, Server
Affects Versions: 6.1.0
Reporter: Van Halbert
Assignee: Van Halbert
Fix For: 6.2.0
Here are the discussed changes to enable connection pool monitoring:
- Create a new stat's class to expose the information: ConnectionPoolStats
- Enable the ConnectionPool to monitor the following pieces of information:
a. Total Connections - Total Number of Connections for the Connection Pool
b Available Connections - Number of available connections in the connection pool.
c Active Connections - Number of Connections currently supporting clients.
d Connections Created - Number of Connections created since the Connection Pool was
created.
e Connections Destroyed - Number of Connections destroyed since the Connection Pool
was created.
In the config.xml for the base Connector component type
a. Rename the ConnectorMaxThreads to MaxConnections so that it
relates better to the user
- Expose the ConnectionPoolStats out the adminAPI
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira