[CAMEL-18255] Memory Leak with MDCUnitOfWork

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.14.1, 3.17.0
• Fix Version/s: 3.14.6, 3.18.4, 3.19.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Michael Rambichler
• Created: 01/Jul/22 15:51
• Updated: 29/Oct/22 06:43
• Resolved: 18/Jul/22 08:18

Description

We realized a sever memory leak in a standard route:

 

I reproduced it and made a simple MemoryAllocation Check.

Just for curiosity i made another test with:  (.errorhandler(no errorhandler)) and the memory leak does not occure.

 

Sample route to reproduce:

 

from("scheduler:testScheduler?repeatCount=1")

                .log("Starting route test-route")

                .process(exchange -> {

                    Iterator<String> infiniteIter = new Iterator<>() {

                        private int integer = 0;

 

                        @Override public boolean hasNext()

{                             return true;                         }

                        @Override public String next()

{                             return String.valueOf(integer++);                         }

                    };

                    exchange.getMessage().setBody(infiniteIter);

                })

                .split().body().streaming()

                    .log("inside split: ${body}")

                .end()

                .log("test-route never finishes");

Issue Links

• duplicates: CAMEL-16034 MDC Logging causing OutOfMemory with large split
• is caused by: CAMEL-17153 afterprocess of UnitOfWork doesn't work properly
• links to: GitHub Pull Request #7987
• links to: GitHub Pull Request #8643
• links to: GitHub Pull Request #8645