Coherence Managed Server Fails to Auto Detect and Load Default Keystore File.
(Doc ID 2322784.1)
Last updated on APRIL 27, 2020
Applies to:Oracle Coherence - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Customer has seen the following errors when starting the managed server that is local storage enabled. The domain is migrated from the 220.127.116.11.x to 12.2.1.x. The below error was not seen in the 12.1.2.x.x but seen in the 12.2.1.x.x. version.
Though the above error got workaround by implementing the suggestion in the <Note 2307827.1> however, it is a temporary fix. Customer do not have the override file. The <ssl> defaults are generally loaded from the default operational override file of the coherence.jar for the managed server. Default configurations are working in the 12.1.2.x.x but failed in the 12.2.1...x.x. SSL is enabled on WebLogic Servers and configured the "custom Identity and custom TrustKeystore" in WLS Admin console.
1. Why the keystore.jks file missing error is appearing from the 18.104.22.168.0 version but not in the previous version(s). What actually changed?
2. Why there is a need to define the keystore in override xml file or specify the -Dtangosol.coherence.security.keystore=file:C:/xxx/xx.jks in server startup? What has changed with coherence 12.2.1.x.x?
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