Hello,
I am facing an execution error after migrate from Elasticsearch 7.6.1 to 7.17.6
on my Spring Boot application (2.6.6) using Camel 3.14.7.
I am using the Elasticsearch High Level Rest Client.
Stacktrace
---------------------------------------------------------------------------------------------------------------------------------------
java.lang.NoClassDefFoundError: org/elasticsearch/common/CheckedConsumer
at
org.apache.camel.component.elasticsearch.ElasticsearchProducer$HighLevelClient.<init>(ElasticsearchProducer.java:347)
~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
at
org.apache.camel.component.elasticsearch.ElasticsearchProducer$HighLevelClient.<init>(ElasticsearchProducer.java:345)
~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
at
org.apache.camel.component.elasticsearch.ElasticsearchProducer.process(ElasticsearchProducer.java:124)
~[camel-elasticsearch-rest-3.14.7.jar:3.14.7]
at
org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66)
~[camel-support-3.14.7.jar:3.14.7]
... 9 more
Wrapped by: org.apache.camel.CamelExecutionException: Exception occurred during
execution on the exchange: Exchange[88DD3EC7DD8FD02-000000000000028B]
at
org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
~[camel-api-3.14.7.jar:3.14.7]
at
org.apache.camel.support.AbstractExchange.setException(AbstractExchange.java:591)
~[camel-support-3.14.7.jar:3.14.7]
at
org.apache.camel.support.DefaultExchange.setException(DefaultExchange.java:27)
~[camel-support-3.14.7.jar:3.14.7]
at
org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:69)
~[camel-support-3.14.7.jar:3.14.7]
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
~[camel-core-processor-3.14.7.jar:3.14.7]
at
org.apache.camel.management.DefaultInstrumentationProcessor.process(DefaultInstrumentationProcessor.java:90)
~[camel-management-3.14.7.jar:3.14.7]
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.redeliver(RedeliveryErrorHandler.java:884)
~[camel-core-processor-3.14.7.jar:3.14.7]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
~[camel-base-engine-3.14.7.jar:3.14.7]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:59)
~[camel-base-engine-3.14.7.jar:3.14.7]
at
org.apache.camel.processor.aggregate.AggregateProcessor.lambda$onSubmitCompletion$4(AggregateProcessor.java:893)
~[camel-core-processor-3.14.7.jar:3.14.7]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
~[?:?]
at java.lang.Thread.run(Thread.java:834) ~[?:?]
---------------------------------------------------------------------------------------------------------------------------------------
Same problem was described on Stackoverflow but nobody found a solution :
https://stackoverflow.com/questions/70666910/apache-camel-elasticsearch-endpoint-failing-with-classnotfoundexception-org-ela
I tried to upgrade to Camel 3.20.3 but the error is still there.
Could the solution be to migrate to Elasticsearch Java Api Client ?
Thanks in advance for your help
Thomas Cousin
[bandeau_pagesjaunes3]<https://www.youtube.com/playlist?list=PLlp-0-iXtsZMOsEKlmySbkrj7VNjqUOfH>
[bandeau_partenaires]<https://www.solocal.com>
Les informations contenues dans le présent message sont strictement
confidentielles et ne sont destinées qu'à l'usage de la ou des personne(s) dont
le nom apparaît en qualité de destinataire(s) et de tout autre personne
spécifiquement autorisée à les recevoir. Si vous n'êtes pas la personne à qui
ce message est destiné, nous vous informons qu'il est strictement interdit de
le lire, diffuser, de le distribuer ou d'en faire des copies, totalement ou
partiellement, sur tout support, notamment un support électronique, ou autre.
La présente interdiction s'applique tant au message lui-même qu'aux documents
qui peuvent être joints audit message. Si vous recevez ce message par erreur,
nous vous remercions de bien vouloir le détruire ainsi que toute copie et de
signaler l'erreur à l'envoyeur par retour d’e-mail.
