Hi Are you sure that your old camel app works with Camel 4.6.0, and then start failing in 4.7.0 onwards ? And the link to CAMEL-2214 is a mistake, what is the correct jira number?
And mind that sync executor service is a bit of a "hack" as the executor service supposed is not supposely to be depent on ordering. But we know that people may use this hack to allow original thread to block until entire splitter is complete before continuting, and then its gets very complication when you have parallel processing or whatnot in the mix. Anyway you are welcome to provide an easy to run sample project (as small as possible). And you can also create a JIRA. No promise that we will change the core in Camel because of this. On Fri, Feb 13, 2026 at 8:33 PM Michael Parmeley < [email protected]> wrote: > After we upgraded camel from 4.4.x to 4.10.0 we started getting a > StackOverflowError in our routes that used a streaming splitter with an > aggregation that uses SynchronousExecutorService. After much > experimentation I was able to create a unit test that recreates the > problem. After trying many different versions of camel I determined the > regression was introduced in Camel 4.7.0 and it still remains in the newest > Camel 4.17.0. > > I have a gradle project containing a single test that makes the unit test > very easy to run with any camel version you want. I was going to open a > Jira with the project attached but then saw you are supposed to contact the > mailing list first. > > The regression I have found seems very similar to > https://issues.apache.org/jira/browse/CAMEL-2214; however, my route is a > little different than that one and continues to throw a StackOverflowError. > That one is splitter+transaction, mine is > splitter+streaming+aggregation+SynchronousExecutorService. (the unit test > in that issue no longer throws a Stackoveflow) > > Is anyone else having this issue? Should I open a Jira with my unit test? > > -- Claus Ibsen
