See more
See less

Connection Leak Profiling:Weblogic

  • Filter
  • Time
  • Show
Clear All
new posts

  • Connection Leak Profiling:Weblogic

    A Connection leak occurs when a connection from the pool is not closed explicitly by calling close()on that connection.
    When connection leak profiling is active, the connection pool will store the stack trace at the time the Connection object is allocated from the connection pool and given to the client. When a connection leak is detected (when the Connection object is garbage collected), this stack trace is reported.
    This option is required to view leaked connections from the connection pool (right-click the connection pool name and select View Leaked Connections).

    This feature uses extra resources and will likely slow down connection pool operations, so it is not recommended for production use.


    Attribute: ConnLeakProfilingEnabled

    To enable Connection Leak Profiling from weblogic console:

    In the JDBC Connection Pool—>Configuration—>Connections tab, click on Advanced options.

    Click Enable Connection Leak Profiling then hit apply.
    Verify config.xml that ConnLeakProfilingEnabled is set to true, if not, restart the admin server instance then verify again.

    “how to monitor the connection leakage after enabling the connection leak profile”

    Viewing Leaked Connections

    After enabling automatic leaked connection recovery, you can view statistics about connections that leaked from a connection pool:
    1. In the left pane, click to expand the Services, JDBC, and Connection Pool nodes to display the list of connection pools in the current domain.
    2. Right-click the connection pool that you suspect is leaking connections and select View Leaked Connections. If any connections leaked and were recovered, information about the application that reserved the connection is displayed in the right pane.