Java Changes in Security Policies Break Coherence Application Settings
(Doc ID 1958710.1)
Last updated on APRIL 28, 2020
Applies to:Oracle Coherence - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When a coherence application is running in a Java runtime which has the security manager enabled, it is denied access to configuration files, even if those configuration files are located in the same EAR lib directory as the coherence.jar.
For example, with the configuration files stored in a jar file located in the EAR lib directory along with the coherence.jar file, the following errors are reported with the security manager enabled:
Other libraries, such as log4j, can access their configuration files if they are in the same location as the code. The Java documentation states you should never have to grant permission as an application should always be able to access files in the same
directory or subdirectory.
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