[
https://issues.apache.org/jira/browse/CAMEL-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106986#comment-14106986
]
Mariano Gonzalez edited comment on CAMEL-7733 at 8/22/14 3:36 PM:
------------------------------------------------------------------
>From my understanding whenever we do a call to the camel cache component using
> the following header:
{code:xml}
<setHeader headerName="CamelCacheOperation">
<constant>CamelCacheDeleteAll</constant>
</setHeader>
{code}
Is when the cache-backing file needs to change. In my case like [~jvz] that is
not happening.
was (Author: eschizoid):
>From my understanding whenever we do a call to the camel cache component using
> the following header:
{code:xml}
<setHeader headerName="CamelCacheOperation">
<constant>CamelCacheDeleteAll</constant>
</setHeader>
{code:xml}
Is when the cache-backing file needs to change. In my case like [~jvz] that is
not happening.
> Sending a CamelCacheDeleteAll does not actually delete anything
> ---------------------------------------------------------------
>
> Key: CAMEL-7733
> URL: https://issues.apache.org/jira/browse/CAMEL-7733
> Project: Camel
> Issue Type: Bug
> Components: camel-cache
> Affects Versions: 2.13.2
> Environment: Karaf 3.0.1, CentOS 6
> Reporter: Matt Sicker
> Priority: Minor
>
> Sending a CamelCacheOperation of CamelCacheDeleteAll doesn't actually delete
> anything from the cache. It might be clearing out the in-memory cache, but
> anything that's persisted to disk won't be cleared. This causes immense
> problems anytime a stray class gets serialized that had its serialization
> format updated. Constant exceptions from attempting to get items from the
> cache is not what should be happening here.
> If I delete the cache file EHCache is using, that obviously does nothing as
> it still has a file handle on it and will continue using it unless I
> completely restart Karaf.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
