Camel-cache component has a default ehcache.xml file embedded and it is used for configuring ehcache. It configures 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 configure file from camel-cache component jar. We should either remove it from camel-cache jar to allow fallback to ehcache-failsafe.xml from ehcache library or modify the ehcache.xml to avoid relying on multicast.