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.
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. 14. The method of claim 9 , wherein the profile information includes a cached statements profile indicating which client added the cached statements.