camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Heesemann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9316) LevelDBAggregationRepository is logging warnings when exchange is already complete on first aggregation
Date Mon, 16 Nov 2015 09:36:11 GMT

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

Justin Heesemann commented on CAMEL-9316:
-----------------------------------------

I'm using completionTimeout(getTimeout()).completionPredicate(isFinished())

So when a message enters the aggregation step, it may a) be complete already because of the
completionPredicate or b) it will complete another message

Think of a simple string concatenating aggregator and a completionPredicate that says string.length
> 3.
when you send a string "abcd" it is already complete by itself.
if you send "ab" and never something that matches, it will timeout somewhen..


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

Mime
View raw message