[CAMEL-18844] Possible memory leak in org.apache.camel.impl.console.EventConsole

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.20.0
• Fix Version/s: 3.20.1, 3.21.0, 4.0-M1, 4.0.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Rafał Gała
• Created: 27/Dec/22 14:29
• Updated: 30/Jan/23 08:59
• Resolved: 29/Dec/22 08:23

Description

Today I have upgraded from 3.18.4 to 3.20.0 and did tests under heavy load as usual. After processing of approximately 3 millions of exchanges JVM's heap usage reached 4GB and it ran out of memory. I analyzed a dump in Eclipse MAT and it showed the following:

One instance of org.apache.camel.spring.boot.SpringBootCamelContext loaded by org.apache.catalina.loader.ParallelWebappClassLoader @ 0x700b5adb0 occupies 3 276 629 016 (97,38%) bytes. The memory is accumulated in one instance of java.lang.Object[], loaded by <system class loader>, which occupies 3 276 529 992 (97,38%) bytes.Keywordsorg.apache.camel.spring.boot.SpringBootCamelContextorg.apache.catalina.loader.ParallelWebappClassLoader @ 0x700b5adb0java.lang.Object[]

I discovered that the java.util.ArrayDeque instance in org.apache.camel.impl.console.EventConsole instance (most probably the exchangeEvents one) contains references to over 12 millions of various org.apache.camel.impl.event.* objects, like ExchangeCreatedEvent, ExchangeSentEvent etc.

I will investigate this further, but it looks like the poll method on ArrayDeque does not do something as expected or is used in a wrong way

 

Issue Links

• relates to: CAMEL-18847 camel-console - We need a camel-console-support JAR