Jdbc Monitoring and Diagnostics Enhancements

1. A system comprising: a computer including a processor, memory, and application server operating thereon, wherein the application server enables access between one or more client applications and a database; a JDBC subsystem associated with the application server, wherein the JDBC subsystem includes a connection pool which includes a plurality of connections for use by the client applications in communicating requests to the database, a prepared statement cache which includes a plurality of previously parsed requests that can be reused by the client applications and communicated to the database, a profiling component which maintains profile information concerning the connection pool and the prepared statement cache, wherein the profile information includes a connection usage profile indicating which particular client applications are currently using a connection or a prepared statement with the database, and a statistics monitoring component which maintains cumulative or averaged information concerning usage of the connection pool and the prepared statement cache over all of the client applications; and wherein the system enables a diagnostic image to be created which includes the profile information and the cumulative or averaged information for applications that are being monitored by the JDBC subsystem.

2. The system of claim 1 , wherein the connection usage profile indicates when a pool connection was reserved by a client.

3. The system of claim 1 , wherein the profile information includes a wait profile indicating which client is currently waiting for a connection.

4. The system of claim 1 , wherein the profile information includes a wait failure profile indicating which client waited for a connection.

5. The system of claim 1 , wherein the profile information includes a connection leak profile indicating which client reserved a connection and did not use the connection.

6. The system of claim 1 , wherein the profile information includes a cached statements profile indicating which client added the cached statements.

7. The system of claim 1 , wherein the profile information includes a statement executed profile indicating which client executed the cached statements.

8. The system of claim 1 , wherein the profile information includes a statement executed profile indicating how long the execution of the cached statements took.

9. A method of providing a diagnostic image for a JDBC subsystem, comprising the steps of: providing a computer including a processor, memory, and application server operating thereon, wherein the application server enables access between one or more client applications and a database; providing a JDBC subsystem associated with the application server, wherein the JDBC subsystem includes a connection pool which includes a plurality of connections for use by the client applications in communicating requests to the database, a prepared statement cache which includes a plurality of previously parsed requests that can be reused by the client applications and communicated to the database, a profiling component which maintains profile information concerning the connection pool and the prepared statement cache, wherein the profile information includes a connection usage profile indicating which particular client applications are currently using a connection or a prepared statement with the database, and a statistics monitoring component which maintains cumulative or averaged information concerning usage of the connection pool and the prepared statement cache over all of the client applications; and creating a diagnostic image which includes the profile information and the cumulative or averaged information for applications being monitored by the JDBC subsystem.

10. The method of claim 9 , wherein the connection usage profile indicates when a pool connection was reserved by a client.

11. The method of claim 9 , wherein the profile information includes a wait profile indicating which client is currently waiting for a connection.

12. The method of claim 9 , wherein the profile information includes a wait failure profile indicating which client waited for a connection.

13. The method of claim 9 , wherein the profile information includes a connection leak profile indicating which client reserved a connection and did not use the connection.

14. The method of claim 9 , wherein the profile information includes a cached statements profile indicating which client added the cached statements.

15. The method of claim 9 , wherein the profile information includes a statement executed profile indicating which client executed the cached statements.

16. The method of claim 9 , wherein the profile information includes a statement executed profile indicating how long the execution of the cached statements took.

17. A computer readable medium, including instructions stored thereon which when read and executed by a computer cause the computer to perform the steps comprising: providing an application server that enables access between one or more client applications and a database; providing a JDBC subsystem associated with the application server, wherein the JDBC subsystem includes a connection pool which includes a plurality of connections for use by the client applications in communicating requests to the database, a prepared statement cache which includes a plurality of previously parsed requests that can be reused by the client applications and communicated to the database, a profiling component which maintains profile information concerning the connection pool and the prepared statement cache, wherein the profile information includes a connection usage profile indicating which particular client applications are currently using a connection or a prepared statement with the database, and a statistics monitoring component which maintains cumulative or averaged information concerning usage of the connection pool and the prepared statement cache over all of the client applications; and creating a diagnostic image which includes the profile information and the cumulative or averaged information for applications being monitored by the JDBC subsystem.

18. The computer readable medium of claim 17 , wherein the connection usage profile indicates when a pool connection was reserved by a client.

19. The computer readable medium of claim 17 , wherein the profile information includes a wait profile indicating which client is currently waiting for a connection or which client waited for a connection.

20. The computer readable medium of claim 17 , wherein the profile information includes a cached statements profile indicating which client added the cached statements or which client executed the cached statements.