How to Avoid Broadcast (Multicast) Storms in Replicated Cache Topology?

(Doc ID 787256.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Coherence - Version 3.3.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

In an application that runs on WebLogic Application Server 9.2 and which uses Coherence for Hibernate L2 cache (for an application cache.), network monitoring tools report broadcast storms on the Coherence multicast address.

There is a need to eliminate the broadcast storms while preserving the replicated cache. What are some possible approaches?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms