Bug #36948 | Trying to use trustCertificateKeyStoreUrl causes an IllegalStateException. | ||
---|---|---|---|
Submitted: | 26 May 2008 8:41 | Modified: | 19 Apr 2012 21:16 |
Reporter: | Robert Fitzsimons | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[26 May 2008 8:41]
Robert Fitzsimons
[28 May 2008 8:39]
Tonci Grgin
Test case, ExportControlled.java rev.6774
Attachment: TestBug36948.java (text/java), 2.78 KiB.
[28 May 2008 8:42]
Tonci Grgin
Hi Robert and thanks for your report. Verified just as described with test case attached (find all details inside) even though Mark made new revision yesterday after we discussed this. Workaround is rather simple; remove &trustCertificateKeyStoreUrl=c:\jvms\jdk1.5.0\bin\bug36948&trustCertificateKeyStorePassword=****** (and for client too) and put it into code: System.setProperty("javax.net.ssl.keyStore","c://jvms//jdk1.5.0//bin//bug36948"); System.setProperty("javax.net.ssl.keyStorePassword","*****"); System.setProperty("javax.net.ssl.trustStore","c://jvms//jdk1.5.0//bin//bug36948"); System.setProperty("javax.net.ssl.trustStorePassword","******");
[23 Jul 2008 8:49]
Tonci Grgin
Bug#38192 was marked as duplicate of this report.
[19 Apr 2012 21:16]
John Russell
Added to changelog for 5.1.7: When using trustCertificateKeyStoreUrl or clientCertificateKeyStoreUrl, an IllegalStateException was caused by an uninitialized TrustManagerFactoryImpl object.
[6 Jul 2016 10:36]
Richard Bradley
Related to this, I have found that if I specify "clientCertificateKeyStoreUrl" but not "trustCertificateKeyStoreUrl" as connection URL parameters I get the "TrustManagerFactoryImpl is not initialized" IllegalStateException. It would be more helpful if the connector failed with a message like "'trustCertificateKeyStoreUrl' is required if 'clientCertificateKeyStoreUrl' is specified"