[
https://issues.apache.org/jira/browse/CAMEL-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857391#comment-16857391
]
Barbara De Vido commented on CAMEL-13616:
-----------------------------------------
Sorry, I forgot about the mailing list.
Anyway, searching in the mailing list I found a similar problem, reported in
April:
http://camel.465427.n5.nabble.com/Issue-Camel-not-clearing-inflight-repository-td5832747.html#a5832885
I'll check the properties for our routes, to see if my problem depends on the
value allowUseOriginalMessage in Camel context.
Thank you!
> Exchange are not removed from InflightRepository
> ------------------------------------------------
>
> Key: CAMEL-13616
> URL: https://issues.apache.org/jira/browse/CAMEL-13616
> Project: Camel
> Issue Type: Bug
> Components: came-core
> Affects Versions: 2.22.1
> Environment: Apache Camel 2.22.1
> Reporter: Barbara De Vido
> Priority: Major
>
> Hi,
> we have a very wired behaviour in some of our routes.
> It seems like the exchanges are not removed from the inflight repository when
> they are done.
> I have a route monitoring the inflights on all the other routes deployed and
> the report I obtain show increasing inflight exchages in the observed
> context. When we stop the context the log reports something like thousand
> inflight messages, but we know for sure that those messages are ended and
> should not be there.
> This is an example of the report:
> {noformat}
> contextId: oda-context
> route Id: creazione-oda-jde
> exchange Id: ID-fdda49c87575-1559495115491-0-30069
> duration Minutes: 2557.947
> contextId: prg-viaggi-context
> route Id: creazione-viaggio-JDE-cancellazione-riga-di-stato
> exchange Id: ID-14699b28ba59-1559498643691-0-73768
> duration Minutes: 1174.142
> {noformat}
> The "creazione-viaggio-JDE-cancellazione-riga-di-stato" uses a
> ProducerTemplate and creates a new exchange for the send method.
> And I'm quite sure also the other route uses a ProducerTemplate....
> Also, the "prg-viaggi-context" has a multicast but not in the routeId where
> the inflight is.
> If we do not manually stop the context, at some point, we cannot even check
> for inflights becasue we get this error from the browse() method of jmx bean:
> {noformat}
> RuntimeException thrown in RequiredModelMBean while trying to invoke
> operation browse
> ... KeyAlreadyExistsException ... Argument value's index, calculated
> according to this TabularData instance's tabularType, already refers to a
> value in this table.
> {noformat}
> It sounds like the exchange is duplicated in the repository ???
> I have no idea how to collect more information in order to resolve this. But
> maybe someone had the same problems and can help me.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
