"Server is sending a non-null replay context but our replayModes=" Using ojdbc8.jar Within Java Unit Testing Against An 18.5 Database
(Doc ID 2539833.1)
Last updated on FEBRUARY 26, 2021
Applies to:JDBC - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Thin JDBC driver
Problems when using ojdbc8.jar within Java Unit Testing against an 18.5 database
Several users have been hit with the same error when using the new ojdbc8.jar file to connect within their Java Unit testing environment against an RDBMS 18.5 database service. The error message is below.
Using the ojdbc7.jar (18.104.22.168) fixed the problem, for others, the fix was to use the default service name of the database, but this last one is not a good option. The service created (srvctl add service -d dbname....) did not contain anything unusual.
The odd fact here, is that the same connection information, outside the Java Unit Testing environment (Oracle, Maven) actually works perfectly.
The problem is inside the Unit Testing.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document