With the Camel 4.14.3 update, the camel-elasticsearch feature needed changes. Since then, the camel-elasticsearch test never ends. I suspect it's related to the dual HTTP client versions in the feature: the resolver maybe has two chains, causing infinite mutations.
With the Camel 4.14.3 update, the camel-elasticsearch feature needed changes. Since then, the camel-elasticsearch test never ends.
I suspect it's related to the dual HTTP client versions in the feature: the resolver maybe has two chains, causing infinite mutations.