JDBC Connection To The Database via Certificate Takes Much Longer Than With Password
(Doc ID 2732085.1)
Last updated on JUNE 29, 2023
Applies to:
JDBC - Version 12.2.0.0.0 to 18.0.0.0.0 [Release 12c to 18c]Information in this document applies to any platform.
Symptoms
A connection to the database via a certificate takes much longer than with password.
Versions:
The Oracle JDBC Thin driver version is 12.2.0.1.0.
Oracle Database server version is 12.1.0.2.0
JDK version is 1.8.0.241
Example:
A series of tests were done, as outlined below, running the test application directly on the database server i.e. behind the firewall, but to the same database/user.
First, connecting to the SCAN:
Password 670 ms 45 ms
JKS keystore 730 ms 85 ms
PKCS12 keystore 1200 ms 690 ms
Wallet 710 ms 120 ms
Secondly to the VIP:
Password 500 ms 55 ms
JKS keystore 560 ms 100 ms
PKCS12 keystore 1200 ms 700 ms
Wallet 700 ms 170 ms
And finally directly to the VIP IP address:
Password 450 ms 50 ms
JKS keystore 550 ms 75 ms
PKCS12 keystore 900 ms 500 ms
Wallet 650 ms 120 ms
So whilst these are faster than those seen when there is network/firewall between the client and server, the differences for connection methods are still apparent, with the PKCS#12 keystore still a lot slower than the other methods.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |