Coherence Cluster Proxy Node JMX reports Garbled after Rolling Upgrade to 220.127.116.11.x and 14c
(Doc ID 2851035.1)
Last updated on FEBRUARY 24, 2022
Applies to:Oracle Coherence - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Customer reported that Coherence Cluster Proxy JMX Reports garbled after rolling upgrade to 22.214.171.124.11. User did a rolling upgrade, starting from WLS clients, Coherence Cluster proxy nodes, then the cache nodes. On Proxy nodes (proxy1 and proxy2) the Reporting Service is running. After few weeks user noticed that, the report-proxy was garbled on both proxies. We expect it contains N lines per batch: one batch for each proxy. Instead, the well-formed lines were only those related to the node itself, whilst the other ones were missing from all data. User had tried to restart the reporter service on reporting proxy nodes via JMX console, with no success.
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