ORMIS SSL Configuration Ignored In OC4J Instances When keyStore Or TrustStore Are Specified As Startup Options In opmn.xml
(Doc ID 1524507.1)
Last updated on AUGUST 15, 2022
Applies to:
Oracle Containers for J2EE - Version 10.1.3.3.0 to 10.1.3.5.0 [Release AS10gR3]Information in this document applies to any platform.
Symptoms
The problems can be reproduced in any 10.1.3.3/4/5 OC4J instances which have been configured to use keyStore and trustStore for its client SSL connections, but this affects directly to the RMIS listener configuration producing different sets of symptoms, which can vary depending on the previous RMIS configuration
That means that the involved OC4J instance has been configured with java options
so that its uses that trustStore/keystore for its client SSL communication against remote peers.
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 |