Connection Usage

            Collect information about threads currently using connections from the pool
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - connection ID
            * User - stack trace of the thread using the connection
            * Timestamp - time stamp showing when the connection was given to the thread

             Sample:  

  ####<DemoDataSource1 > <WEBLOGIC.JDBC.CONN.USAGE> <Wed Apr 23 07:39:02 EST 2014> <java.lang.Exception
            at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:356)
            at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:364)
            at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:471)
            at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:363)

            …

Connection Reservation Wait
            Collect information about threads currently waiting to reserve a connection from the data source
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - thread ID
            * User - stack trace of the thread waiting for the connection
            * Timestamp - time stamp showing when the thread started waiting for a connection

             Sample:   

####< DemoDataSource1> <WEBLOGIC.JDBC.CONN.RESV.WAIT> <0> < . . .
            {Stack Trace for waiting thread}
            ...

Connection Reservation Failed

            Collect information about threads that fail to reserve a connection from the pool
            Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - thread ID
            * User - stack trace of the thread waiting for the connection plus the exception received when the reservation request failed
            * Timestamp - time stamp showing when the reservation request failed

             Sample:  
  ####< DemoDataSource1> <WEBLOGIC.JDBC.CONN.RESV.FAIL> <Tue Apr 23 15:38:03 CEST 2014> <weblogic.common.resourcepool.ResourceDisabledException: Pool DBADAPTERDSXA is Suspended, cannot allocate resources to applications..

Connection Leak

            Collect information about threads that have reserved a leaked connection from the pool
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - connection ID
            * User - stack trace of the thread waiting for the connection
            * Timestamp - time stamp showing when the connection leak was detected

             Sample:  
  < DemoDataSource1> <WEBLOGIC.JDBC.CONN.LEAK> <java.lang.Exception
            at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:356)
            at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:364)
            at weblogic.jdbc.common.internal.HAConnectionPool.reserve(HAConnectionPool.java:206)
            at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:129)
            …

Connection Last Usage

            Collect information about the previous thread that last used the connection
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - stack trace of the XA exception thrown
            * User - stack trace of the thread that last used the connection
            * Timestamp - time stamp showing when the exception was thrown

             Sample:  
  ####< DemoDataSource1> <WEBLOGIC.JDBC.CONN.LAST_USAGE> <0> < . . .
            {Stack Trace for thread that last used the connection}
            ...

Connection Multithreaded Usage

            Collect information about threads that erroneously use a connection that was previously obtained by a different thread
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - stack trace of the other thread that was found using the connection
            * User - stack trace of the thread that reserved the connection
            * Timestamp - time stamp showing when usage of the connection by multiple threads was detected

             Sample: 
   ####< DemoDataSource1> <WEBLOGIC.JDBC.CONN.MT_USAGE> <Fri Apr 18 04:57:20 PST 2014> <java.lang.Exception
            at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:356)
            at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:364)
            at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:330)
            ...

Statement Cache Entry

            Collect information for threads that caused prepared and callable statements added to the statement cache
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - string representation of the statement
            * User - stack trace of the thread using the statement
            * Timestamp - time stamp showing when the statement was added to the cache

             Sample:  
  ####< DemoDataSource1> <WEBLOGIC.JDBC.STMT_CACHE.ENTRY> <Tue Apr 11 16:42:43 EST 2014> <java.lang.Exception
            at weblogic.jdbc.common.internal.ConnectionPoolProfiler.addStmtCacheEntryData(ConnectionPoolProfiler.java:246)
            at weblogic.jdbc.common.internal.ConnectionEnv.getCachedStatement(ConnectionEnv.java:1309)
            at weblogic.jdbc.common.internal.ConnectionEnv.getCachedStatement(ConnectionEnv.java:1216)
            at weblogic.jdbc.common.internal.ConnectionEnv.getCachedStatement(ConnectionEnv.java:1209)
            ...

Statements Usage

            Collect information about threads currently executing SQL statements from the statement cache
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - SQL statement being executed via the statement
            * User - stack trace of the thread using the statement
            * Timestamp - duration of statement execution

             Sample:  
  ####< DemoDataSource1> <WEBLOGIC.JDBC.STMT.USAGE> <0> <java.lang.Exception at
            . . .
            weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run( ContainerSupportProviderImpl.java:254)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)
            > <select 1 from dual>

Connection Unwrap

            Collect information about thread that accesses the JDBC connection using either the 'getVendorObject' WebLogic extension API or the JDBC 4.0 method 'unwrap'
             Data Collected:
            * PoolName - name of the data source to which this connection belongs
            * ID - stack trace of where the object was unwrapped
            * User - stack trace of the thread unwrapping the object
            * Timestamp - time stamp showing when the object was unwrapped

             Sample:    
####< DemoDataSource1> <WEBLOGIC.JDBC.CONN.RESV.WAIT> <0> < . . .
            {Stack Trace for unwrapping thread}
            ...

1 Comments

  1. Hi,

    I'm already run the diagnostics metrics to store the in Persistent FIle Store, I've run dump the .DAT file to a xml file but when I open it I see the following below:

    3663904: 2e45 7863 6570 7469 6f6e 0a09 6174 2077 .Exception..at w
    3663920: 6562 6c6f 6769 632e 6a64 6263 2e63 6f6d eblogic.jdbc.com
    3663936: 6d6f 6e2e 696e 7465 726e 616c 2e43 6f6e mon.internal.Con
    3663952: 6e65 6374 696f 6e50 6f6f 6c50 726f 6669 nectionPoolProfi
    3663968: 6c65 722e 6164 6453 746d 7443 6163 6865 ler.addStmtCache
    3663984: 456e 7472 7944 6174 6128 436f 6e6e 6563 EntryData(Connec
    3664000: 7469 6f6e 506f 6f6c 5072 6f66 696c 6572 tionPoolProfiler
    3664016: 2e6a 6176 613a 3233 3929 0a09 6174 2077 .java:239)..at w
    3664032: 6562 6c6f 6769 632e 6a64 6263 2e63 6f6d eblogic.jdbc.com
    3664048: 6d6f 6e2e 696e 7465 726e 616c 2e43 6f6e mon.internal.Con
    3664064: 6e65 6374 696f 6e45 6e76 2e67 6574 4361 nectionEnv.getCa
    3664080: 6368 6564 5374 6174 656d 656e 7428 436f chedStatement(Co
    3664096: 6e6e 6563 7469 6f6e 456e 762e 6a61 7661 nnectionEnv.java
    3664112: 3a31 3233 3129 0a09 6174 2077 6562 6c6f :1231)..at weblo
    3664128: 6769 632e 6a64 6263 2e63 6f6d 6d6f 6e2e gic.jdbc.common.
    3664144: 696e 7465 726e 616c 2e43 6f6e 6e65 6374 internal.Connect
    3664160: 696f 6e45 6e76 2e67 6574 4361 6368 6564 ionEnv.getCached
    3664176: 5374 6174 656d 656e 7428 436f 6e6e 6563 Statement(Connec
    3664192: 7469 6f6e 456e 762e 6a61 7661 3a31 3133 tionEnv.java:113
    3664208: 3829 0a09 6174 2077 6562 6c6f 6769 632e 8)..at weblogic.
    3664224: 6a64 6263 2e63 6f6d 6d6f 6e2e 696e 7465 jdbc.common.inte
    3664240: 726e 616c 2e43 6f6e 6e65 6374 696f 6e45 rnal.ConnectionE
    3664256: 6e76 2e67 6574 4361 6368 6564 5374 6174 nv.getCachedStat
    3664272: 656d 656e 7428 436f 6e6e 6563 7469 6f6e ement(Connection
    3664288: 456e 762e 6a61 7661 3a31 3133 3129 0a09 Env.java:1131)..
    3664304: 6174 2077 6562 6c6f 6769 632e 6a64 6263 at weblogic.jdbc
    3664320: 2e77 7261 7070 6572 2e43 6f6e 6e65 6374 .wrapper.Connect
    3664336: 696f 6e2e 7072 6570 6172 6553 7461 7465 ion.prepareState
    3664352: 6d65 6e74 2843 6f6e 6e65 6374 696f 6e2e ment(Connection.

    how can I see the metrics collected in the format that you shows in this post.

    Regards

    ReplyDelete