camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Klimczak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-3849) OSGi - No possibility to enable ehcache clustering as: ehcache.xml is ignored and there is no possibility to set cacheManagerFactory described camel-cache docs
Date Mon, 11 Apr 2011 09:47:05 GMT

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

Piotr Klimczak commented on CAMEL-3849:
---------------------------------------

Great! Sound like a fun! Will do that soon :)

> OSGi - No possibility to enable ehcache clustering as: ehcache.xml is ignored and there
is no possibility to set cacheManagerFactory described camel-cache docs
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3849
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3849
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cache
>    Affects Versions: 2.6.0, 2.7.0
>         Environment: Apache ServiceMix 4.3.1-fuse-01-09
>            Reporter: Piotr Klimczak
>            Assignee: Claus Ibsen
>              Labels: cacheManagerFactory, camel-cache, cluster, clustering, osgi
>             Fix For: 2.8.0
>
>         Attachments: camel-cache.patch
>
>
> This bug is caused by more than one problem as:
> 1. camel-cache bundle provides ehcache.xml config which is ignored so then default ehcache-failsafe.xml
is taken by ehcache bundle.
> 2. according to camel-cache docs there is a way to set cacheManagerFactory but it seems
to be not implemented as
> a) default CacheManagerFactory instance is created when when CacheComponent is instantiated.
> b) setter method: public void setCacheManagerFactory(CacheManagerFactory cacheManagerFactory)
is used just nowhere.
> c) there is no suitable filed in class CacheConfiguration
> All above problems cause camel-cache to be not able to work in java- clustered world
as default failsafe config. is really failsafe- w/o clustering.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message