"java.lang.Throwable: Connection leak found: created statck" Error Encountered Causing PRIMARY_JTS to be Exhausted (Doc ID 1449807.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 6.1.5 and later
Information in this document applies to any platform.
***Checked for relevance on 12-Nov-2013***

Symptoms


PRIMARY_JTS connection pool leak issue - pool grows till exhausted. The following message in found in the exception logs:

java.lang.Throwable: Connection leak found: created statck

java.lang.Throwable: Connection leak found: created statck
at glog.util.j2ee.jdbc.ASJTSConnection.<init>(ASJTSConnection.java:23)
at glog.util.j2ee.jdbc.ASConnectionEstablisher.connect(ASConnectionEstablisher.java:44)
at glog.util.j2ee.jdbc.WLConnectionPoolInstance.reserve(WLConnectionPoolInstance.java:46)
at glog.util.j2ee.jdbc.ASConnectionPoolInstance.reserve(ASConnectionPoolInstance.java:60)
at glog.util.datasource.AppServerConnectionPool.reserve(AppServerConnectionPool.java:34)
at glog.util.datasource.DataSource.reserve(DataSource.java:143)
at glog.util.datasource.DataSource.reserve(DataSource.java:137)
at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:298)
at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:288)
at glog.util.jdbc.noserver.T2SharedConnection.open(T2SharedConnection.java:55)
at glog.server.query.JDBCConnection.open(JDBCConnection.java:30)
at glog.server.query.JDBCFinder.openConnection(JDBCFinder.java:289)
at glog.server.query.JDBCFinder.open(JDBCFinder.java:151)
at glog.server.query.ListRetrieverBean.retrieve(ListRetrieverBean.java:39)
at glog.server.query.query_ListRetriever_whmeh3_EOImpl.retrieve(query_ListRetriever_whmeh3_EOImpl.java:61)
at glog.server.query.query_ListRetriever_whmeh3_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Finalizer

PRIMARY_JTS pool continues to grow until application issues arise (i.e. “connection pool overloaded” condition, as well as error: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool PRIMARY_JTS to allocate to applications, please increase the size of the pool and retry..).

To circumvent, a recycle is necessary or increase max connections.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms