Justin Heesemann created CAMEL-9316:
---------------------------------------
Summary: 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
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)
