[jira] Issue Comment Edited: (DBCP-292) Adds an mbean for exposing metrics around a BasicDataSource via JMX

["Alexandru Ionita (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DBCP-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839120#action_12839120 ] 

Alexandru Ionita edited comment on DBCP-292 at 2/27/10 1:46 AM:
----------------------------------------------------------------

When registering the bean org.apache.commons.dbcp.BasicDataSource directly into Spring's MBeanExporter, you get the bean registered in the JMX stack. 

What I have observed is that by each Refresh button hit in the JMX jconsole, the NumActive is increased with 2 !!! Basically, the jconsole is consuming two connections from the pool (don't know why) for each refresh without releasing them. 

      was (Author: iga):
    When registering the bean org.apache.commons.dbcp.BasicDataSource directly into Spring's MBeanExporter, you get the bean registered in the JMX stack. 

What I was observing is that by each Refresh button hit in the JMX jconsole, the NumActive is increased with 2 !!! Basically, the jconsole is consuming two connections from the pool (don't know why) for each refresh without releasing them. 
  
> Adds an mbean for exposing metrics around a BasicDataSource via JMX
> -------------------------------------------------------------------
>
>                 Key: DBCP-292
>                 URL: https://issues.apache.org/jira/browse/DBCP-292
>             Project: Commons Dbcp
>          Issue Type: New Feature
>    Affects Versions: 1.2.2
>            Reporter: David Horne
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: BasicDataSourceMBean.patch
>
>
> The attached patch adds an mbean that exposes the following metrics of a BasicDataSource via jmx: numActive, numIdle, maxActive, maxIdle, minIdle & maxWait.
> I have put it in a new package: org.apache.commons.dbcp.management but feel free to put it in any package you see fit.
> If using Spring the bean can be configured a little something like this:
> <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">
>  ...
> </bean>
> <bean id="dataSourceMBean" class="org.apache.commons.dbcp.management.BasicDataSourceMBean">
> 	<constructor-arg ref="dataSource"/>
> </bean>
> <bean id="mbeanExporter" class="org.springframework.jmx.export.MBeanExporter">
> 	<property name="beans">
> 		<map>
> 			<entry key="DBCP:name=dataSource" value-ref="dataSourceMBean"/>
> 		</map>
> 	</property>
> </bean>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.