camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7195) Default ehcache.xml configure from camel-cache jar should not rely on multicast
Date Wed, 12 Feb 2014 13:26:19 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899079#comment-13899079
] 

Willem Jiang commented on CAMEL-7195:
-------------------------------------

Hi Joe,

You should be able to override the default configuration by apply a new configuration like
this.
{code}
    CacheComponent cache = context.getComponent("cache", CacheComponent.class);
    cache.setConfigurationFile("classpath:test-ehcache.xml");
{code}

If you want to do the configuration per endpoint you can let cache endpoint lookup the cache
manager factory like this 
{code}
       String CACHE_ENDPOINT_URI =
            "cache://myname1?cacheManagerFactory=#testCacheManagerFactory";
       CacheManagerFactory testingCacheManagerFactory = new FileCacheManagerFactory("src/test/resources/test-ehcache.xml");
       jndi.bind("testCacheManagerFactory", testingCacheManagerFactory);
{code}

You can find more examples of those configuration from the unit tests of camel-cache.


> 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)

Mime
View raw message