-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Warning: Multiple httpclient implementation in the classpath #32937
Comments
/cc @Sgitario (kubernetes), @evanchooly (kotlin), @geoand (kotlin,kubernetes), @iocanel (kubernetes) |
Can you add the output of |
Sure.
|
That's interesting as it looks like there is only one dependency bringing in an client implementation. Would it be possible to attach a sample application so we can debug and find out what's going on? Thanks |
@geoand I'v added a reproducer in the description for the warning "There are multiple httpclient implementation in the classpath, choosing the first non-default implementation. ..." |
It should work in dev mode as well AFAIR. I won't have time to look into it, but I don't think there is another build item |
@Sgitario Do you think that the presence of multiple http clients ist the cause of the KubernetesClientException (not contained in the reproducer)? If not, then there is a additional issue in Quarkus 3.0.1. |
I didn't hit into the Can you try to reproduce it running the application using the JAR file instead of running it in DEV mode? |
Yes. It cant bei reproduced with my reproducer, only the warning. I guess the "wrong" http client is chosen and this leads to the KubernetesClientException.
I will try. |
The warning disappeard in prod mode (running the jar). But I continue to see the |
This would definitely be another issue, different from this one. Please, report a new issue with the steps we can follow to reproduce it (I could not see this error), so we can help you better. |
After annotating all REST methods with |
The exception should be unrelated to the warning, but I might be wrong. I will try to take a look at what's going on as well, but probably not before next Wednesday. |
Results summarized so far:
|
/cc @shawkins The log warning should be fixed now. Regarding the second problem (timeout), looks very similar to fabric8io/kubernetes-client#5091 (comment). Maybe caused by a deadlock and having only one IO thread available to process the HTTP response results. |
I can confirm that the warning no longer appears in Quarkus 3.0.2.Final.
Seems likely |
Or at least it will be clearer what the situation is - the may still be a warning log, but it will indicate what all of the implementations are. |
What's the status of this in Quarkus |
The second problem (timeout) still exists. Has the kubernetes client been upgraded to 6.6.0 in Quarkus 3.2.0.CR1 (see fabric8io/kubernetes-client#5091)? |
We have moved even further: https://mvnrepository.com/artifact/io.quarkus/quarkus-kubernetes-client/3.2.0.CR1 |
Is this still a problem with Quarkus 3.8? |
I cannot reproduce it anymore. |
Thanks a lot for checking! |
Describe the bug
I wanted to upgrade one of our applications from Quarkus 2.16.6.Final to Quarkus 3.0.1.Final. The application starts but as soon as I use the Kubernetes client I get the following warning and exception in the console:
I guess the exception is due to the warning that there are multiple HTTP clients on the classpath?
Maven dependencies:
How to Reproduce?
reproducer.zip
./mvnw quarkus:dev
Output of
java -version
Java 17
Quarkus version or git rev
3.0.1.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3.9.1
The text was updated successfully, but these errors were encountered: