This content has been marked as final. Show 1 reply
SL makes RTView OCM, a monitoring tool for Coherence so we have a lot of experience with this. Its all too easy to stress the JMX Mbean server and see the publisher success rate go below 99% with larger clusters (in terms of the # of mbeans). This especially can happen when you are querying mbean data faster than the JMX node can return the data. Its also typical during cluster startup when every node is registering mbeans with the JMX node as they join the cluster.
I assume you have a dedicated JMX node and that you have management=all only on that node? I assume that the PublisherSuccessRate is less than 99% only on the JMX node and that you have a tool calculating this rather than looking at the JMX mbean value (which is calculated as an average from the node start time)?
How many mbeans do you have in the cluster? Are you polling for every MBean? How often? We find it takes 1 msec/mbean to retreive data (best case scenario). Worst case scenario is much higher.