camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bjørn Hilstad (JIRA) <>
Subject [jira] [Commented] (CAMEL-8086) Possible memoryleak when convertBodyTo is used in a dynamicRouter
Date Thu, 27 Nov 2014 20:38:12 GMT


Bjørn Hilstad commented on CAMEL-8086:

I'm not quite sure that we could use a recipient list in this case.
What we are trying to do is to make a while-loop, where we in the bean get one message from
an external service and process that. If there are no more messages the bean will return null
to exit from the dynamic router.

> Possible memoryleak when convertBodyTo is used in a dynamicRouter
> -----------------------------------------------------------------
>                 Key: CAMEL-8086
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.13.2
>            Reporter: Bjørn Hilstad
>            Priority: Minor
> We have implemented a while loop using a dynamicRouter.
> The dynamicRouter looks like this:
> <dynamicRouter>
>   <header>someheadername</header>
> </dynamicRouter>
> where someheadername refers to another route using direct:routename
> The route that handles direct:routename looks like this:
> <bean ref="someref"/>
> <convertBodyTo type="java.lang.String"/>
> The someref-bean just puts some data in the body and header and would also be responsible
to set the value of someheadername=null to exit the dynamicRouter.
> During execution of these routes we see that heapusage increases until OOM if the dynamicRouter
does not exit before OOM. The number of instances of DefaultMessage also keeps increasing.
> If we remove the <convertBodyTo> from the route we do not get OOM and the number
of instances of DefaultMessage is stable and low.
> The same also happens if we replace <convertBodyTo> with a <transform>.

This message was sent by Atlassian JIRA

View raw message