New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Camel-quarkus-couchbase Consumer is not working #3283
Comments
This works fine on Camel-plain |
I adapted the Camel csimple example with the route mentioned above and observed the same issue. Whenever Jackson is added to the classpath, it triggers the error. |
I'll try again the kamelets using Jackson just for confirmation. |
Thanks for checking |
ah ok, now I'm getting your message. If you run this https://github.com/apache/camel-examples/tree/main/examples/couchbase-log The error we are seeing on camel-quarkus is not showing up and the route is the same. This is true with 3.13.0-SNAPSHOT and 3.11.1/3.11.2 So I'm not sure this is a problem on plain camel |
Btw with csimple adapted I don't have errors
and the route is
|
cc @davsclaus |
Sorry - maybe I confused things here a bit. I only chose csimple because it was easy to hack and add couchbase. I didn't see the couchbase-log example..... The underlying issue is with adding Jackson libs to the classpath (E.g via |
In csimple example I added the camel-jackson dep and It didn't fail for me. |
Add |
Oh, silly me. I was under the impression you were using the csimple example as is. Sorry for that. |
Let me see what is happening |
In 3.1.4 couchbase client is using jackson-databind 2.12.2 and in 3.2.0 2.12.3, while Camel 3.13.x is using 2.12.4 and Camel 3.11.x is using 2.12.3. It's weird. |
Excluding jackson-databind from camel-jackson, make it works. Ok they're shading databind. |
Thanks @jamesnetherton Definitely not a problem of camel or camel-quarkus. |
Suppose to run
docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase:6.5.1
and to create sample bucket "beer-sample" with the sample data by creating a user admin/password
Now run a simple route
This will fail badly with
The text was updated successfully, but these errors were encountered: