1、weblogic Connection Leak 連接池泄漏問(wèn)題解決2009-06-25 10:37如果程序有問(wèn)題， weblogic 里um Capacity 設(shè)置多大，都會(huì)泄漏的。你設(shè)置 50 Active Connections Current Count 變?yōu)?50，設(shè)置為 100，它變?yōu)?100，所以這時(shí)應(yīng)該檢查程序了。默認(rèn) weblogic 是不這個(gè)泄漏日志的，只會(huì)報(bào) jdbc 錯(cuò)誤。以下內(nèi)容部分，部分是實(shí)際遇到，但解決步驟雷同，原文地址：1、修改登錄 weblogic console, % - Servi- JDBC - Connection Pools - jdbc/ioaCo

2、nfiguration 頁(yè) - Connection, 點(diǎn)開(kāi) Advanced Options, 修改以下配置項(xiàng)狀態(tài)：2、 以上配置項(xiàng)修改后不影響在跑的應(yīng)用，不需要重啟服務(wù)器或應(yīng)用（配置項(xiàng)前沒(méi)有黃色小圖標(biāo) ，WebLogic 很明確的告訴這個(gè)配置是不需要重啟的），所以大可放心設(shè)置。只是啟用后會(huì)對(duì)性能有一些影響，具體影響會(huì)有多大，我沒(méi)有測(cè)試過(guò)，但開(kāi)啟這些設(shè)置只是暫時(shí)的，得到日志后原會(huì)默認(rèn)值。就可以把配置還在沒(méi)有解決連接池泄漏問(wèn)題之前，如果沒(méi)有請(qǐng)求時(shí)連接池將一直保持為 0，不會(huì)再有連接池滿造成請(qǐng)求無(wú)法響應(yīng)解決問(wèn)題爭(zhēng)取了寶貴到時(shí)間。，也不用擔(dān)心再挨客戶罵，也為好了，下面才是關(guān)鍵。過(guò)一段時(shí)間后，在be

3、auser_projectss%name%servername%目錄下，打開(kāi)%servername%.log，查找，A JDBC pool connection leak was detected，如果 WebLogic 已經(jīng)到有連接池泄漏的話，就可以找到以下日志，并且很清楚的告訴體）：在哪一個(gè)類的哪行代碼創(chuàng)建了連接，但沒(méi)有關(guān)閉（注意紅色加粗字2008-5-22CST上午 11 時(shí) 47 分 20 秒WarningJDBCA配置項(xiàng)名稱默認(rèn)值修改為說(shuō)明Enable Connection Leak Profiling禁用啟用開(kāi)啟連接池泄漏的。Enable Connection Profiling禁

4、用啟用開(kāi)啟連接池。Inactive Connection Timeout0100連接在指定時(shí)間內(nèi)（ ：秒）沒(méi)有活的話，WebLogic 會(huì)將之 并回收到接池。JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by callingclose() and then was dised by the garbage collector and returned tothe connecti

5、on pool. The following stack trace at create shows where the leaked connection was created. Stack trace at connection create:at weblogic.jdbc.wrappoolConnection.init(PoolConnection.java:75)at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:254)at weblogic.jdbc.pool.Driver.connect(Driver.jav

6、a:84)at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:546)at weblogic.jdbc.jts.Driver.connect(Driver.java:140)atmon.ernal.RmiDataSource.getConnection(RmiDataSource.java:344)at com.cp.fw.Base.getConnection(Base.java:78)at.dataset.DataSetOp.init(DataSetOp.java:78)com.cp.fw.at.dataset.DataSet

7、Op.(DataSetOp.java:45)com.cp.fw.at com.cp.ia.util.WorkFlowUtil.getNextWrokFlowId(WorkFlowUtil.java:93)at另外法：在 WebLogic Console，展開(kāi) %Name% - Servers - %ServerName%，選到 Logging Server 頁(yè)，在頁(yè)面最下方點(diǎn)擊 View server log，同樣查找 A JDBC pool connection leak was detected，也可以找到同樣的日志。WebLogic 對(duì)于日志事件的說(shuō)明：Message ID BEA-00

8、1074 Subsystem JDBCMessage A JDBC pool connection leak was detected. Aconnection leak occurs when a connection obtainedfrom the pool was not closed explicitly by callingclose() and then was dised by the garbagecollector and returned to the connection pool. Thefollowing stack trace at create shows wh

9、ere theleaked connection was created. Stack trace atconnection create:Detail A JDBC pool connection leak was detected. Aconnection leak occurs when a connection obtainedfrom the pool was not closed explicitly by callingclose() and then was discollector and returned to the connection pool. Astack trace is pred indicating where the leakedconnection was created.Cause A JDBC pool connection leak was detected. Aconnection leak occurs when a connection obtainedfrom the pool was not closed explicitly by callingclose() and then was dised by the garbagecollector and returned to the connection poo