[
https://issues.apache.org/jira/browse/CAMEL-20301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske resolved CAMEL-20301.
------------------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
Fixed with https://github.com/apache/camel/pull/12722
> Camel retains objects when restarting route via policy
> ------------------------------------------------------
>
> Key: CAMEL-20301
> URL: https://issues.apache.org/jira/browse/CAMEL-20301
> Project: Camel
> Issue Type: Bug
> Components: came-core
> Affects Versions: 4.0.3
> Reporter: Sebastian Brandt
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Fix For: 4.4.0
>
>
> When restarting a route using a RoutePolicy, Camel seems to retain objects
> related to the stopped route, preventing the GC from reclaiming those.
> Heap dump analysis indicated that the objects are retained by
> org.apache.camel.impl.engine.DefaultRoute.services
> I've created a minimal reproducer in
> [https://github.com/sebastian-brandt/RoutePolicyIssue] using a route with a
> seda consumer.
> The issue becomes more apparent when the restarted route uses a consumer
> component that itself uses more memory (e.g. netty).
> The accumulated old objects eventually lead to OOM error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
