[
https://issues.apache.org/jira/browse/CAMEL-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Luo updated CAMEL-7195:
---------------------------
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:
{code}
<cacheManagerPeerProviderFactory
class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
properties="peerDiscovery=automatic,
multicastGroupAddress=230.0.0.1,
multicastGroupPort=4446, timeToLive=1"
propertySeparator=","
/>
{code}
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.
was:
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:
{code}
<cacheManagerPeerProviderFactory
class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
properties="peerDiscovery=automatic,
multicastGroupAddress=230.0.0.1,
multicastGroupPort=4446, timeToLive=1"
propertySeparator=","
/>
{code}
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 failsafe to ehcache-failsafe.xml file from ehcache
library or modify the embedded ehcache.xml to avoid relying on multicast.
> Default ehcache.xml configure from camel-cache jar should not rely on
> multicast
> --------------------------------------------------------------------------------
>
> Key: CAMEL-7195
> URL: https://issues.apache.org/jira/browse/CAMEL-7195
> Project: Camel
> Issue Type: Bug
> Components: camel-cache
> Affects Versions: 2.10.3
> Reporter: Joe Luo
>
> 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:
> {code}
> <cacheManagerPeerProviderFactory
> class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
> properties="peerDiscovery=automatic,
> multicastGroupAddress=230.0.0.1,
> multicastGroupPort=4446, timeToLive=1"
> propertySeparator=","
> />
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
