Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <16609194.15621282737287998.JavaMail.jira@thor>
Date: Wed, 25 Aug 2010 07:54:47 -0400 (EDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-3077) Cache Component needs to check for
 null values during GET operations
In-Reply-To: <26007763.14911282706747392.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/CAMEL-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3077.
--------------------------------

         Assignee: Claus Ibsen
    Fix Version/s: 2.5.0
       Resolution: Fixed

trunk: 989026.

Thanks for the patch.

> Cache Component needs to check for null values during GET operations
> --------------------------------------------------------------------
>
>                 Key: CAMEL-3077
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3077
>             Project: Apache Camel
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>         Environment: Received 2.4.0 release of Camel and Camel Cache component from Maven repo
>            Reporter: John Ellis
>            Assignee: Claus Ibsen
>             Fix For: 2.5.0
>
>         Attachments: CacheProducer.NPE.patch
>
>
> EhCache often has a bit of lag time when invalidating expired cache elements, first setting the Element value to null and then removing the key. If you are hitting a cache rapidly one often will run across a key that is present in the cache that still has a null element entry.
> The logic for successfully key retrieval just needs to be slightly tweaked to check for null values.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.