support tomcat jdbc pool about javamelody HOT 7 CLOSED

That would be a great enhancement.
Could you make a patch? Thanks

Dev guide: http://code.google.com/p/javamelody/wiki/DevGuide

It's possible to use tomcat jdbc pool with javamelody without a patch:

      Properties props = new Properties();
      props.setProperty("driver", YOUR_REAL_JDBC_DRIVER_CLASS);

      org.apache.tomcat.jdbc.pool.DataSource datasource = null;
      PoolConfiguration p = new PoolProperties();
      p.setDriverClassName("net.bull.javamelody.JdbcDriver");
      p.setDbProperties(props);
      p.setUsername("dbuser");
      p.setPassword("dbpass");
      p.setUrl("dburl");
      datasource = new org.apache.tomcat.jdbc.pool.DataSource();
      datasource.setPoolProperties(p);
      ConnectionPool pool = datasource.createPool();

@mineral_wasser
I think that you were misguided by the title of this issue.
I suppose that monitoring the connections of the tomcat jdbc pool was always 
supported,
either by using the default monitoring of jdbc datasources from JNDI,
or by using the javamelody JdbcDriver as you have written.
See http://code.google.com/p/javamelody/wiki/UserGuide#7._JDBC if needed

But given the description of the issue, the reporter wanted in fact that 
javamelody displays the specific configuration of the tomcat jdbc pool (max 
open connections, max open prepared statements, validation queries, etc), 
because javamelody displays these specific configuration for the tomcat DBCP 
pool, but javamelody does not currently display the same specific configuration 
for the newer tomcat jdbc pool.

http://code.google.com/p/javamelody/source/browse/trunk/javamelody-core/src/main
/java/net/bull/javamelody/JdbcWrapperHelper.java#248

Ah, I see.
Thanks for the clarification, evernat!
(I would also love to see this)

Another thing - I think it would be better to use jdbc pools JDBCInterceptors 
to "hook" into jdbc call than a using a JDBC Proxy driver, which feels a little 
bit more dangerous. 

The enhancement is now done in trunk (revision 2747) and ready for the next 
release (1.37). It will display the properties of the Tomcat jdbc datasources 
in System informations like for Tomcat DBCP, in particular it will display the 
max number of active connections next to the current number of active 
connections.

If you want to test it before the next release, I have made a new build which 
is available at:
http://javamelody.googlecode.com/files/javamelody-20120419.jar

My App has a tomcat jdbc connection pool deployed over tomcat7.I am unable to 
see "active jdbc connections","used jdbc connections" and sql hits using java 
melody.Any help will appreciated.

@megha
This issue has nothing to do with what you said.