Takut, Bersyukur, Tawakkal

Alhamdulillah, another step closer to Pertamina

Showing Leaked Connection Stacktrace in WebLogic Server

This afternoon I was get very anxious about what shows in cgServer.log and nohup.out.

####Nov 6, 2006 5:35:16 PM WIT Warning JDBC galaxydev1 cgServer Finalizer anonymous BEA-001074 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.

But no stacktrace is printed there! Oh, how much I'am willing to fix that leaked connection.

Thank God, by just simply tick Enable Connection Leak Profiling from [domain_name]> JDBC Connection Pools> [connection_pool_name], the stacktrace was hanging there nicely.

Stack trace at connection create:

at weblogic.jdbc.wrapper.JTAConnection.init(JTAConnection.java:76)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:409)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
at com.indosat.csf.dao.DAOConnectionImp.getDBConnection(DAOConnectionImp.java:76)
at com.indosat.csf.geneva.adapter.CProductAccount.getProductId(CProductAccount.java:119)
at com.indosat.csf.geneva.adapter.CProductAccount.getProductList(CProductAccount.java:185)
at com.indosat.csf.geneva.adapter.CProductAccount.getProductbyAccount(CProductAccount.java:325)
at com.indosat.csf.process.main.modules.SearchProductbyAccount.perform(SearchProductbyAccount.jpd:130)

Yes! Next problem please ...