[CAMEL-7195] Default ehcache.xml configure from camel-cache jar should not rely on multicast

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10.3
• Fix Version/s: 2.12.3, 2.13.0
• Component/s: camel-cache
• Estimated Complexity: Unknown
• Assignee: Grzegorz Grzybek
• Reporter: Joe Luo
• Created: 12/Feb/14 10:53
• Updated: 19/Dec/19 17:29
• Resolved: 13/Feb/14 07:46

Description

Camel-cache component has a default ehcache.xml file embedded and it is used for configuring ehcache. It configures a cacheManagerPeerProviderFactory to use a built-in RMI-based distribution system by default which unfortunately relies on multicast:

<cacheManagerPeerProviderFactory         class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic,
                        multicastGroupAddress=230.0.0.1,
                        multicastGroupPort=4446, timeToLive=1"
            propertySeparator=","
            />

It sometimes causes a problem when deploying a camel cache route due to multicast/network configuration on it's host.

We should not rely on multicast in default ehcache configuration that is enforced by ehcache.xml from camel-cache component jar. We should either remove it from the jar to allow fallback to ehcache-failsafe.xml file from ehcache library or modify the embedded ehcache.xml to avoid relying on multicast.