WebLogic 8.1.6 환경에서 연결 풀에서 누출된 코드를 찾는 방법


[size=large]
         
  weblogic console,  %Domain% -> Services -> JDBC -> Connection Pools -> jdbc/ioa

 

Configuration  -> Connection,   Advanced Options,          :

 

     
    
    
   
 
Enable Connection Leak Profiling
   
   
           。
 
Enable Connection Profiling
   
   
        。
 
Inactive Connection Timeout
 0
 100
         (  : )      ,WebLogic            。
 

 

                    ,           (            <!--[if !vml]--><!--[endif]-->,WebLogic                   ),        。                ,        ,      ,            ,                   。


              ,                0,                   ,            ,                。

 

         ,      。

 

             , bea\user_projects\domains\%domainname%\%servername%   ,  %servername%.log,  ,"A JDBC pool connection leak was detected",  WebLogic             ,         ,                         ,     (        ):






 

2008-5-22   11 47 20  CST       Warning     JDBC                A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the connection pool. The following stack trace at create shows where the leaked connection was created. Stack trace at connection create: 

       at weblogic.jdbc.wrapper.PoolConnection.init(PoolConnection.java:75)

       at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:254)

       at weblogic.jdbc.pool.Driver.connect(Driver.java:84)

       at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:546)

       at weblogic.jdbc.jts.Driver.connect(Driver.java:140)

       at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:344)

       at com.cp.fw.dao.BaseDAO.getConnection(BaseDAO.java:78)

       at com.cp.fw.dao.dataset.DataSetOp.init(DataSetOp.java:78)

       at com.cp.fw.dao.dataset.DataSetOp.<init>(DataSetOp.java:45)

       at com.cp.ia.util.WorkFlowUtil.getNextWrokFlowId(WorkFlowUtil.java:93)

       at 

 

……

       

 

             :



 WebLogic Console,   %DomainName% -> Servers -> %ServerName%,  Logging – Server ,         "View server log",     "A JDBC pool connection leak was detected",          。

 

WebLogic         :

 

Message ID
 BEA-001074
 
Subsystem
 JDBC
 
Message
 A JDBC pool connection leak was detected. A 

connection leak occurs when a connection obtained 

from the pool was not closed explicitly by calling 

close() and then was disposed by the garbage 

collector and returned to the connection pool. The 

following stack trace at create shows where the 

leaked connection was created.  Stack trace at 

connection create:
 
Detail
 A JDBC pool connection leak was detected. A 

connection leak occurs when a connection obtained 

from the pool was not closed explicitly by calling 

close() and then was disposed by the garbage 

collector and returned to the connection pool. A 

stack trace is printed indicating where the leaked 

connection was created.
 
Cause
 A JDBC pool connection leak was detected. A 

connection leak occurs when a connection obtained 

from the pool was not closed explicitly by calling 

close() and then was disposed by the garbage 

collector and returned to the connection pool. A 

stack trace is printed indicating where the leaked 

connection was created.
 
Action
 Close the connection appropriately.
 


  :http://blog.csdn.net/esky2000/archive/2008/07/22/2689929.aspx 


[/size]

좋은 웹페이지 즐겨찾기