OPSS - What are the JDBC Connections Settings Recommended for OPSS DataSource? (Doc ID 2298612.1)

Last updated on AUGUST 01, 2023

Applies to:

Goal

Some of the OPSS DataSources / JDBC Connections Are Not Using Recommended Settings Out of the Box.

The Oracle recommendations are here:

Connection Testing Options for a Data Source

The following OPSS datasources:

opss-audit-DBDS (opss-audit-jdbc.xml)
opss-audit-viewDS (opss-auditview-jdbc.xml)
opss-data-source (opss-datasource-jdbc.xml)

Should have the following parameters set out of the box based on the documentation

a)<inactive-connection-timeout-seconds>600</inactive-connection-timeout-seconds>

    This is a general recommendation and consists on setting a value within the inactive-connection-timeout-seconds helps not to have leaked connections.
    Ideally, you won't have any leaked connections coming from our own software, but that doesn't mean it is not a good generic recommendation.
    Also if you take a look into other data sources from other of our products they normally have this type of value.

b)<connection-creation-retry-frequency-seconds>10</connection-creation-retry-frequency-seconds>

    This is a general recommendation. This parameter represents the number of seconds between attempts to establish connections to the database. Typically the value can vary depending
    on the application expectation, but a value between 10-30 seconds is reasonable.
    Also if you take a look into other data sources from other of our products they normally have this type of value.

 c) <test-connections-on-reserve>true</test-connections-on-reserve>

    This is a general recommendation. Data sources rely on the Test Reserved Connections
    (test-connections-on-reserve) feature on the data source to know when database connectivity is lost or there are connectivity issues, and for simplicity.
    This parameter enables WebLogic Server to test a connection before giving it to a client, eg, in this case OPSS.
    Also if you take a look into other data sources from other of our products they normally have this type of value.

d) <test-frequency-seconds>300</test-frequency-seconds>

    This is a general recommendation.  The test-frequency-seconds element allows you to specify how frequently (in seconds) connections in the pool are tested for viability.
    Also if you take a look into other data sources from other of our products they normally have this type of value.

e) <seconds-to-trust-an-idle-pool-connection>60</seconds-to-trust-an-idle-pool-connection>

    This is a general recommendation.  This is the number of seconds after a connection has been proven to be OK
    that WebLogic Server trusts the connection is still viable and will skip the connection test, either before delivering it to an application or during the
    periodic connection testing process. This option is an optimization that minimizes the performance impact of connection testing, especially during heavy traffic.
    

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.