Last updated on JULY 12, 2017
Applies to:Oracle Coherence - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
A user was experienced the below error after upgrading to 12.2.1.x.x version. User was seen this error on storage nodes of whole cluster, user doesn't use any custom key associations in cache config, and also user can't find the code in 12.2.1.x.x stack trace of error as mentioned in the old NOTE:1636676.1. The documentation page mentioned that it's not a bug but why it was reported as an Error severity message in the logs.
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