Data Source Becomes Overloaded After the JDBC URL Has Been Changed (Doc ID 2306197.1)

Last updated on SEPTEMBER 14, 2017

Applies to:

Oracle SOA Suite - Version 11.1.1.7.8 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.8 version, Fabric

ACTUAL BEHAVIOR
---------------
Data Source becomes overloaded after a change in the JDBC URL was made. The SOADataSource connection count raises gradually until the limit is reached. The SOADataSource then becomes overloaded and the SOA managed server needs to be restarted.

EXPECTED BEHAVIOR
-----------------------
The Data Source should not become overloaded after a change to the JDBC URL.

Changes

 JDBC URL got changed, it is observed that LOAD_BALANCE is set to "off".


jdbc:oracle:thin:@(DESCRIPTION_LIST = (LOAD_BALANCE = off) (FAILOVER = on)(DESCRIPTION = (CONNECT_TIMEOUT = 10)(TRANSPORT_CONNECT_TIMEOUT = 3)(RETRY_COUNT = 3) (ADDRESS_LIST = (LOAD_BALANCE = off) (FAILOVER = on)(ADDRESS = (PROTOCOL = TCP)(HOST = ssc01-c1-scan.vtb24.ru)(PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = szp)))(DESCRIPTION = (CONNECT_TIMEOUT = 10) (TRANSPORT_CONNECT_TIMEOUT = 3)(RETRY_COUNT = 3) (ADDRESS_LIST = (LOAD_BALANCE = off)(FAILOVER = on)(ADDRESS = (PROTOCOL = TCP)(HOST = ssc02-c1-scan.vtb24.ru)(PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = szp))))

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