JDBC Replay Driver Retaining Memory On WebLogic 12.2.14 (Doc ID 3074384.1)

Last updated on MARCH 03, 2025

Applies to:

Symptoms

After setting the replay driver oracle.jdbc.replay.OracleDataSourceImpl in WebLogic 12.2.1.4 datasource using JDBC 19.16, the memory grows until it fills up and causes a system shutdown. The issue does not occur if the Reply driver is not used.
The memory usage growth is gradual during several days until the outofmemory occurs (which is typically seen after about a month). This forces a restart of the instances in the production environment for the memory to be released.

The issue occurs with the application not being in use. That is, the issue reproduces just by configuring the TAC service and the datasource with the Replay driver with no application in execution.

The issue presents itself under the following conditions:

- Test Connection On Reserve + Test Frequency 1 + oracle.jdbc.replay.OracleDataSourceImpl ==> Issue reproduced

- Disabling Test Connection on Reserve but enabling Test Frequency ==> Issue not reproduced

- If the test frequency is set to 0 or the test on reserve is disabled or the oracle.jdbc.OracleDriver is configured, it does not occur. That is:
Test Connection On Reserve + Test Frequency 0 + oracle.jdbc.replay.OracleDataSourceImpl ==> Issue not reproduced
Test Connection On Reserve + Test Frequency 1 + oracle.jdbc.OracleDriver ==> Issue not reproduced

STEPS TO REPRODUCE:

1.Create TAC service

After setting up the datasource, nothing is to be done in addition - no need to connect with the datasource. Just monitor the memory.

Cause

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