weblogic 에러코드(BEA-001074)

# 웹로직 데이타소스에서 DB Connection 누수 현상 발생
# 에러로그는 아래와 같습니다.
# 그런데, 에러 로그를 봐서는 어느 부분에서 문제를 일으키는 것을 알 수 없습니다.

<2005. 4. 25. 오전 9시 55분 7초 KST> <Warning> <JDBC> <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.  [Null exception passed, creating stack trace for offending caller]
 at weblogic.utils.StackTraceUtils.throwable2StackTrace(StackTraceUtils.java:28)
 at weblogic.jdbc.wrapper.PoolConnection.finalizeInternal(PoolConnection.java:84)
 at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.finalize(Unknown Source)
 at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
 at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
 at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
 at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
 
# 그래서,
# 웹로직 관리자 콘솔의 Services > JDBC > Connection Pools 메뉴에서
# 해당 Connection Pool의 Connections > Advances Options 메뉴의
# Enable Connection Leak Profiling 부분을 첵크해 주었습니다.
# 세상에.. DB 커넥션을 구천으로 떠돌게 했던 범인이 잡혔네요. ^^

<2005. 4. 26. 오후 12시 34분 39초 KST> <Warning> <JDBC> <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.  Stack trace at connection create:

 at weblogic.jdbc.wrapper.PoolConnection.init(PoolConnection.java:56)
 at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:254)
 at weblogic.jdbc.pool.Driver.connect(Driver.java:164)
 at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:507)
 at weblogic.jdbc.jts.Driver.connect(Driver.java:139)
 at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
 at com.gmdat.common.RDBConnectionTop.getConnection(RDBConnectionTop.java:46)
 at com.gmdat.util.ReserveDAO.chkReserveCount2(ReserveDAO.java:1295)
 at com.gmdat.util.ReserveDAO.deleteReserve2(ReserveDAO.java:1270)
 at jsp_servlet._charm._reservation.__charm_reserv_cancel._jspService(__charm_reserv_cancel.java:172)
 at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6452)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)