[CAMEL-20301] Camel retains objects when restarting route via policy

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.3
• Fix Version/s: 4.0.4, 4.4.0
• Component/s: came-core
• Estimated Complexity: Unknown
• Assignee: Otavio Rodolfo Piske
• Reporter: Sebastian Brandt
• Created: 05/Jan/24 15:38
• Updated: 10/Jan/24 09:24
• Resolved: 09/Jan/24 14:47

Description

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.

Issue Links

• is related to: CAMEL-20231 camel-jasypt - make generators configurable
• links to: GitHub Pull Request #12733