-
Notifications
You must be signed in to change notification settings - Fork 189
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-Infinispan consumer doesn't work #2344
Comments
Thanks for the detailed reproducer, @oscerd ! It sounds like it is failing also in JVM mode? |
Yes, both native and jvm |
I had a quick look at this. The problem seems to be that the endpoint Camel is trying to do autowiring on The workaround for the standalone example project would be to set property |
Yes, I don't think it can be done with kamelet. |
I think this has exposed a little bug because if I tweak
I can open a Camel ticket. |
This seems to fail even with camel-k 1.4.0-SNAPSHOT, quarkus 1.8.1 and camel 3.9.0
|
Not completely sure, it could be related to this: apache/camel-k#2203 |
I'll try to take another look at it. It may be that the |
This happens through kamelet on camel-k, so it may be related to the reported camel-k issue. Let me see if it works with the fix @lburgazzoli is doing. I don't want you to waste your time. |
even with the fix, the error is the same, while running the same example with camel-k 1.4.0-SNAPSHOT or camel-k staging 1.4.0 |
I had another quick look. It is indeed still broken. I think it's related to the order in which things happen. |
Created another Camel ticket: |
You can turn it off on context level (as workaround) |
Filed quarkusio/quarkus#18232 |
Created a follow up to the original closed issue quarkusio/quarkus#18517. |
This is fixed in Quarkus 2.2.x. If you don't provide any |
While trying to create a kamelet source for Infinispan I found out the consumer doesn't work if the Infinispan cluster is secured.
This gives the following exception
How to set up the Infinispan cluster for this purpose (version is 12.0.0.Final)
Download the zip distribution and unzip it somewhere.
Start the server
Create user
Stop the server.
It's important to add encoding to your cache configuration, otherwise consuming events won't work.
You'll need to:
and add the encoding section in the configuration
Restart the server.
The extension will fail immediately. The same configuration with the plain camel component seems to work fine.
I used the camel-quarkus-examples as base.
Here is the example on my fork.
oscerd/camel-quarkus-examples@cce809b
The text was updated successfully, but these errors were encountered: