Applying Patch 20474010: SU Patch [S8H6]: SPURIOUS HARVESTING OF CONNECTION BY Oracle WebLogic Server (WLS) POOL

Applying Patch 20474010: SU Patch [S8H6]: SPURIOUS HARVESTING OF CONNECTION BY WLS POOL

Smart Update patch S8H6 for WebLogic Server 10.3.6.0

Patch 20474010: SU Patch [S8H6]: SPURIOUS HARVESTING OF CONNECTION BY WLS POOL

Related Bug 20474010: SPURIOUS HARVESTING OF CONNECTION BY WLS POOL

Patch Installation Instructions:

- copy content of this zip file with the exception of README file to your SmartUpdate cache directory (MW_HOME/utils/bsu/cache_dir by default)

Ensure that the directory has the write and executable permissions. 

- apply patch using Smart Update utility

cd $MW_HOME/utils/bsu

./bsu.sh -install -patch_download_dir=/MW_HOME/utils/bsu/cache_dir  -patchlist=S8H6 -verbose -prod_dir=/MW_HOME/wlserver_10.3/




Related post:



Applying Patch 19637463: SU Patch [12UV]: Oracle WebLogic Server (WLS) PATCH SET UPDATE 10.3.6.0.10

Connection test failed with the following exception: weblogic.common.resourcepool.ResourceDisabledException: Pool mds-SpacesDS is Suspended, cannot allocate resources to applications..

Connection test failed with the following exception: weblogic.common.resourcepool.ResourceDisabledException: Pool mds-SpacesDS is Suspended, cannot allocate resources to applications..

You may observe datasources going into suspended state. When you try to test the datasource connection, it throws error as above (with the problem datasource name)

Try checking the DB parameters:

SQL> select name, value from v$parameter where name in ('processes', 'sessions', 'transactions');

If the parameters are set to low values, you may want to increase the value of these parameters & restart the database. Often the case may be Processes parameter may have maxed out & increasing it should resolve the issue of datasources going into suspended state.


SQL> alter system set processes = <value> scope = spfile;

System altered.

SQL> alter system set sessions = <value> scope = spfile;

System altered.

SQL> alter system set transactions = <value> scope = spfile;

System altered.

Restart the database


You may also want to increase Max Capacity of problem datasources.

Also consider increasing the timeout value under Domain -> JTA -> Configuration

Connection test failed with the following exception: weblogic.common.resourcepool.ResourceUnavailableException: No resources currently available in pool to allocate to applications. Either specify a time period to wait for resources to become available, or increase the size of the pool and retry..

Connection test failed with the following exception: weblogic.common.resourcepool.ResourceUnavailableException: No resources currently available in pool to allocate to applications. Either specify a time period to wait for resources to become available, or increase the size of the pool and retry..

- Go to the WebLogic Server Console

- Go to the Console Tree panel on the left hand side & select ""Services"--> JDBC--> Datasources--->Select the appropriate datasource connection pool name

- Select Lock and Edit

- Modify the initial capacity and maximum capacity values.

- Select activate changes

- Re-start Weblogic domain if necessary.