My Oracle Support Banner

BEA-000620 Forcibly releasing inactive resource, currentUser=null,Stack trace is null (Doc ID 2159840.1)

Last updated on MAY 01, 2018

Applies to:

Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Information in this document applies to any platform.


On : 10.3.6 version, WLS Datasource

When attempting to releasing inactive resource
the following error occurs.

####<Jul 11, 2016 5:57:49 PM CST> <Warning> <Common> <ora-kevin> <AdminServer> <[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1468231069532> <BEA-000620> <Forcibly releasing inactive resource "autoCommit=true,enabled=true,isXA=false,isJTS=false,vendorID=100,connUsed=false,doInit=false,'null',destroyed=false,poolname=JDBC Data Source-1,appname=null,moduleName=null,connectTime=28,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=false,lastSuccessfulConnectionUse=1468230994566,



defaultClientInfo={},supportIsValid=true" back into the pool "JDBC Data Source-1".>

The issue has the following business impact:
Due to this issue, there are a lot of Warning messages in log file .
BEA-000620 Forcibly releasing inactive resource, But have no any stack trace , do not know which application there is connection leak issues.


To view full details, 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 a vibrant support community of peers and Oracle experts.