Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 15 Nov 2015 07:07:12 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12912534.1447348231000.73773.1447571232175@Atlassian.JIRA>
In-Reply-To: <JIRA.12912534.1447348231000@Atlassian.JIRA>
References: <JIRA.12912534.1447348231000@Atlassian.JIRA>
 <JIRA.12912534.1447348231636@arcas>
Subject: [jira] [Updated] (CAMEL-9316) LevelDBAggregationRepository is
 logging warnings when exchange is already complete on first aggregation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen updated CAMEL-9316:
-------------------------------
    Priority: Minor  (was: Major)

> LevelDBAggregationRepository is logging warnings when exchange is already complete on first aggregation
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-9316
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9316
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-leveldb
>    Affects Versions: 2.15.3
>            Reporter: Justin Heesemann
>            Priority: Minor
>             Fix For: 2.16.2, 2.17.0
>
>
> When using an aggregator with a LevelDBAggregationRepository and you are sending events, that are already complete by themselves (i.e. the fulfill the completionPredicate and they were never really aggregated), there is a lot of warning logging like
> {code}
> Nov 12, 2015 6:00:57 PM org.apache.camel.component.leveldb.LevelDBAggregationRepository confirm
> WARNUNG: Unable to confirm exchangeId [ID-LPNB2331-59378-1447347654170-0-939 from repository collectionNotifications: Not Found]
> {code}
> My guess is that calling confirm on the repository in such cases is unnecessary, but I'm not sure, if it is easy to detect wether confirm should be called or not.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)