[ https://issues.apache.org/jira/browse/CAMEL-16034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Graf updated CAMEL-16034: ---------------------------------- Description: If using MDC logging and splitting a large amount of data it could cause OutOfMemory because internal memory consumption for MDC is growing enormous. DefaultReactiveExecutor.Worker.back in HeapDump seems to be correlated with MDCCallback See test case [^Main.java] run with -Xmx1G -XX:+HeapDumpOnOutOfMemoryError was: If using MDC logging and splitting a large amount of data it could cause OutOfMemory because internal memory consumption for MDC is growing enormous. See DefaultReactiveExecutor.Worker.back in Dump seems to be correlated with MDCCallback See test case [^Main.java] run with -Xmx1G -XX:+HeapDumpOnOutOfMemoryError > MDC Logging causing OutOfMemory with large split > ------------------------------------------------ > > Key: CAMEL-16034 > URL: https://issues.apache.org/jira/browse/CAMEL-16034 > Project: Camel > Issue Type: Bug > Components: camel-core-engine > Affects Versions: 3.7.0 > Reporter: Benjamin Graf > Priority: Major > Attachments: Main.java > > > If using MDC logging and splitting a large amount of data it could cause > OutOfMemory because internal memory consumption for MDC is growing enormous. > DefaultReactiveExecutor.Worker.back in HeapDump seems to be correlated with > MDCCallback > See test case [^Main.java] run with -Xmx1G -XX:+HeapDumpOnOutOfMemoryError -- This message was sent by Atlassian Jira (v8.3.4#803005)