Connection for pool has been closed is coming in Admin server and there is no exception. Any fix?

User_801US

<[STANDBY] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <b5a345> <173765739614> <[severity-value: 64] [rid: 0] > <BEA-001128> <Connection for pool "XXX Data Source" has been closed.> 

Please guide on this how to fix this, there is no exception/error in the logs also.

Ram-Oracle

@User_801US Please confirm the product you are using .Is it obiee ,oracle analytics server?please share the version of product

Login to wls console ,left hand side please expand services and click on data sources .

example: click on biplatform_datasource ,monitoring tab and testing and test the connection.Please verify for all datasources.

Under connection pool tab please verify timeout settings

At the time of the issue i.e when the log is reported ,Did you get a chance to verify the db connection from other tools like sql developer and confirm the test is successful.

It looks like thread is going to standby mode.

After restarting oas server/Obiee Is issue getting fixed .

Please also verify oas tuning parameters

Best Practices Guide for Tuning Oracle® Analytics Server (Doc ID 2866848.2)

Tune weblogic —> and refer below section from the document

Tune Oracle® WebLogic Server (WLS) parameters

This topic describes how to tune the WebLogic Server to optimize the performance of your Oracle® Analytics Server.

Tuning JDBC Data Sources

You can improve Oracle Analytics Server performance and stability by properly configuring the attributes in JDBC data sources in your bi domain.

Increase the Number of Connection Pool

For obiee 12c ,please refer section 2.2.1.1 Increase the Number of Connection Pool

Best Practices Guide for Infrastructure Tuning Oracle® Business Intelligence Enterprise Edition 12c (OBIEE) (Doc ID 2106183.1)

Federico Venturin

Hi @User_801US ,

You mentioned Admin Server, so I'm assuming you are on Oracle Analytics Server.

Is this error preventing your OAS environment to start?

Did the RCU schemas password expire? Did you recently change it? If so, you may need to set a password properly, eventually unlock any locked RCU user, and update the configuration in WebLogic Console with the new details.