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
Attachments
Attachments
Issue Links
- is duplicated by
-
CAMEL-18255 Memory Leak with MDCUnitOfWork
- Resolved