Forum Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48682

**This is a holder issue. Each section should be raised as a new issue as it is
developed with a link from this issue.**

There are a number of areas in JCA that need better management capabilities.
Some of these stats may also reveal the need for new configuration/tuning parameters.

In core JCA:
1) Better visibility on the ManagedConnectionFactory.
This is currently a DynamicMBean that provides basic config parameters, but we could also
provide a proxy/wrapper to provide statistics of operations on the factory and its
ManagedConnections.
a) createManagedConnections
b) matchManagedConnections
c) events on from the listeners

2) Better visibility of the Pool(s)
Only top level statistics are provided (you cannot see the subpools).
The statistics are also not synchronized with the pool (for performance reasons
and also the fact that each stat is retrieved on individual MBean getAttribute requests)
Additional statistics could include wait times when requests are waiting on an empty pool,
idle time of unused connections, etc.

3) Better visibility of the ConnectionManager
Currently this has no visibility for management.
Its main responsibilties are transactions enlistment and security.
e.g. This could show how long is wasted because <track-connection-by-tx/> does not
return the connection the pool until transaction completion.

4) JDBC resource adapter
PreparedStatementCache stats
Query time stats
etc.

5) JMS resource adapter
Message send/receive stats

6) Inbound messaging
Stats for message delivery

7) Transaction inflow
Stats for transaction inflow and also display a list of current inbound transactions

8) Work management
Stats for the work management pools and timers