Return-Path: 
 <issues-return-18445-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-issues-archive@minotaur.apache.org
Delivered-To: apmail-camel-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8DC2311A16
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Fri, 22 Aug 2014 15:36:11 +0000 (UTC)
Received: (qmail 84411 invoked by uid 500); 22 Aug 2014 15:36:11 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 84375 invoked by uid 500); 22 Aug 2014 15:36:11 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 84360 invoked by uid 99); 22 Aug 2014 15:36:11 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2014 15:36:11 +0000
Date: Fri, 22 Aug 2014 15:36:11 +0000 (UTC)
From: "Mariano Gonzalez (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12735961.1408669907609.13189.1408721771276@arcas>
In-Reply-To: <JIRA.12735961.1408669907609@arcas>
References: <JIRA.12735961.1408669907609@arcas>
Subject: [jira] [Commented] (CAMEL-7733) Sending a CamelCacheDeleteAll does
 not actually delete anything
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Mariano Gonzalez commented on CAMEL-7733:
-----------------------------------------

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