Replace deprecated security class in JDBC
Details
| Detail name | Value |
|---|---|
| Changelog Number | 6264 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0 |
| Fix Versions | Exasol 7.1.1 |
| Resolution Date | 2021-09-14 |
Background
When creating connections for secure local Import / Export, the Exasol JDBC driver uses a few classes that have been marked as /deprecated/.
Problem
Starting with Java 9, Java is printing warning messages for such usage, for example
WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.exasol.jdbc.importExport.KeyManager (file:/usr/opt/EXASuite-6/EXASolution-6.1.dev1/bin/Console/exajdbc.jar) to constructor sun.security.tools.keytool.CertAndKeyGen(java.lang.String,java.lang.String) WARNING: Please consider reporting this to the maintainers of com.exasol.jdbc.importExport.KeyManager WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release
At this point, this is only a warning, but in future Java releases, the functionality may break.
Exasol will try to replace the deprecated classes soon.