[jbossts-issues] [JBoss JIRA] (JBTM-3032) Check the connection pool with JMX when using Transactional DataSource
Amos Feng (JIRA)
issues at jboss.org
Wed Jun 20 22:57:00 EDT 2018
[ https://issues.jboss.org/browse/JBTM-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594760#comment-13594760 ]
Amos Feng commented on JBTM-3032:
---------------------------------
BasicDataSourceMXBean is used for exposing some information of the pool via JMX and it needs to set with 'jmxName', such as
{code:xml}
<Resource name="transactionalDataSource" uniqueName="transactionalDataSource" auth="Container" type="javax.sql.XADataSource"
transactionManager="TransactionManager" xaDataSource="h2DataSource" jmxEnabled="true" jmxName="org.apache.commons.dbcp2:name=transactionalDataSource"
factory="org.jboss.narayana.tomcat.jta.TransactionalDataSourceFactory"/>
{code}
> Check the connection pool with JMX when using Transactional DataSource
> ----------------------------------------------------------------------
>
> Key: JBTM-3032
> URL: https://issues.jboss.org/browse/JBTM-3032
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Tomcat
> Reporter: Amos Feng
> Assignee: Amos Feng
>
> Currently the common-dbcp2 only expose the org.apache.commons.dbcp2.PoolableConnectionMXBean for every database connection. And the customer want to check the connection pool with JMX just like org.apach.tomcat.jdbc.pool.jmx.ConnectionPoolMBean
> * getIdle()
> * getSize()
> * getActive()
> * getNumIdle()
> * getNumActibe()
> * getWaitCount()
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbossts-issues
mailing list