Last updated on NOVEMBER 03, 2016
Applies to:Oracle Coherence - Version 18.104.22.168 and later
Information in this document applies to any platform.
A large cluster is configured with a dedicated JMX Management node, which crashes due to an OutOfMemoryError exception. The node is configured with a custom cache configuration file to ensure that it does not join any cache services and that it only starts the invocation service as that is used internally by the Coherence management infrastructure:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms