Administration Console Online Help

If the monitoring statistics that you are seeing indicate that there is a problem in your WebLogic Server domain, you can configure any data source to collect profile information to help you pinpoint the source of the problem. The collected profile information is stored in records in the WLDF Archive.

This page enables you to define diagnostic profiling options for this JDBC data source.

Configuration Options

Name	Description
Profile Connection Usage	Collect profile information about threads currently using connections from the pool of connections in the data source. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Connection Reservation Wait	Collect profile information about threads currently waiting to reserve a connection from the data source. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Connection Leak	Collect profile information about threads that have reserved a connection from the data source and the connection leaked (was not properly returned to the pool of connections). Set the `Inactive Connection Timeout` feature to a positive value to reclaim leaked connections. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Connection Reservation Failed	Collect profile information about threads that attempt to reserve a connection from the data source but fail. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Statement Cache Entry	Collect profile information for prepared and callable statements added to the statement cache, and for the threads that originated the cached statements. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Statement Usage	Collect profile information about threads currently executing SQL statements from the statement cache. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Connection Last Usage	Collect profile information about the previous thread that last used the connection. This information is useful when debugging problems with connections infected with pending transactions that cause subsequent XA operations on the connections to fail. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Connection Multithreaded Usage	Collect profile information about threads that erroneously use a connection previously obtained by a different thread. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Connection Unwrap	Collect profile information about application components that access the underlying JDBC connection using either the getVendorObject WebLogic extension API or the JDBC 4.0 method unwrap MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileType`
Profile Harvest Frequency Seconds	The number of seconds between when WebLogic Server harvests profile data. When set to `0`, harvesting of data is disabled. MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.ProfileHarvestFrequencySeconds` Minimum value: `0` Maximum value: `2147483647`
Driver Interceptor	Specifies the absolute name of the application class used to intercept method calls to the JDBC driver. The application specified must implement the weblogic.jdbc.extensions.DriverInterceptor interface. Weblogic Server will invoke the preInvokeCallback(), postInvokeExceptionCallback(), and postInvokeCallback() methods of the registered application before and after invoking any method inside the JDBC driver. You can use this feature to profile JDBC driver usage and monitor: Methods being executed Any exceptions thrown Time spent inside the driver executing methods MBean Attribute (Does not apply to application modules) : `JDBCConnectionPoolParamsBean.DriverInterceptor` Changes take effect after you redeploy the module or restart the server.

Administration Console Online Help

JDBC Data Source: Configuration: Diagnostics

Configuration Options