-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Quarkus 1.7.0 + Camel-Quarkus Kafka: Failed to configure SaslClientAuthenticator #11411
Comments
Is none interested in it? Or is it something thats totally out of scope here? |
@bframke do you have a reproducer for that ? |
Now I've created one, which gets the error directly on startup. Tested and build with Quarkus 1.7.1 |
can you add some instruction about how to run it ? |
There is a start.sh in the project, which starts the Project with the command I've also named in the first part of the ticket. For now per default Kafka with SASL (example on how to deactivate it is also in the first part of the ticket) can be started with the restart-kafka.sh in the kafka directory. The application will try to connect to the Kafka via SASL, this can be changed with the application.properties, with just commenting out the security part of the application. What needs to be commented out is also in the first part of the ticket |
it does not seems able to connect, what I get is:
The reason is:
|
Yes, you have to start the Kafka first, then the application, default uri to reach the kafka is localhost:9092, if it is not the same on your system there is a kafka broker list in the application.properties, where you can change it |
The reason kafka does not start is:
|
Okay, normally you just need docker-compose, use restart-kafka.sh and thats it. We did not modify the image in any away that we needed to rebuild it. On docker-compose, executed in the same folder where the files are, it normally gets them into it because we add them as a docker-volume |
I'm using that script but does not seem to work (on fedora) |
Okay, on ArchLinux and Ubuntu it did work, mh. Could be that Fedora does not add the docker volumes in the same way as the other two OS do or maybe something need to be changed there, not sure. Never worked with Fedora. Else we have to create a new docker image where the volumes are just in the docker image itself. |
I did try to use plain docker so I have:
and
When starting kafka I keep getting:
I did check the content of the files on the container and they are properly mounted. |
ok, now it is better but I'm getting:
|
Yeah, I got this error with the Bitnami Kafka in Kubernetes. I've increased the socketRequestMaxBytes from 104857600 to 209715200. I guess in your case it should be 419430400 bytes, it should hopefully help in this case |
I've hopefully been able to have everything running and it works, I think the only missing part was that with the latest version of camel-quarkus you need to explicitly add |
ohh, yeah there was a change in camel-quarkus, good to know, thanks. Thought everything I put in there was enough, but I guess for me he pulled it out my local cache. |
@bframke is the issues fixed by adding camel-main ? |
No, in the main project where I did a copy from and where camel-main is already in because of opentracing this still happens. |
so I guess I need some more help to get a working reproducer :) |
Yeah, I'm checking currently again in the reproducer, had some new errors, because of some tests I did some days ago. |
Okay, added the missing camel-main to the reproducer, also just in case upgraded to 1.7.2 (also tested with 1.7.1) and now I get terminated during auth. So we are after the SASL Error from the beginning. So looks like it works with this, maybe we have an bigger error in our project or it is already resolved and we didn't know. |
cool, I'll try to create a reproducer in any case on camel-quarkus so we can spot similar issues in case |
@bframke can we close this issue ? |
Yes, we are away from the original problem. If it occurs anew I will open it, else there will be another one :D |
Describe the bug
After an update from Quarkus 1.5.2 to Quarkus 1.6.0+ (currently tested with 1.7.0 same behavior) we now receive an error message when we try to secure the Kafka Connection in the App, while also using the camel-quarkus kafka component. We are not using Kafka-Streams. We are also not using an Kerberos, only good old configuration and its values.
Error
Application.properties
Jaas-Config for Command
Jaas-Config for Kafka
Run Gradle Task
Docker-Compose Kafka
Kafka with Compose
Expected behavior
Producer can build up the Camel-Route which uses Camel-Quarkus Kafka Consumer.
Actual behavior
Producer can't create the Route because it tries to get a Principal to use Scram mechanism, but can't get it.
To Reproduce
Steps to reproduce the behavior:
Configuration
Screenshots
Environment (please complete the following information):
Output of
uname -a
orver
:Linux bfr-pc 5.7.9-1-MANJARO Switch to the Maven distributed copy of the SubstrateVM annotations #1 SMP PREEMPT Thu Jul 16 08:20:05 UTC 2020 x86_64 GNU/Linux
Output of
java -version
:openjdk version "11.0.7" 2020-04-14
OpenJDK Runtime Environment (build 11.0.7+10)
OpenJDK 64-Bit Server VM (build 11.0.7+10, mixed mode)
GraalVM version (if different from Java): 20.1
Quarkus version or git rev: 1.7.0
Build tool (ie. output of
mvnw --version
orgradlew --version
):Gradle 6.5.1
Build time: 2020-07-15 13:08:58 UTC
Revision:
Kotlin: 1.3.72
Groovy: 2.5.11
Ant: Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM: 11.0.7 (Oracle Corporation 11.0.7+10)
OS: Linux 5.7.9-1-MANJARO amd64
The text was updated successfully, but these errors were encountered: