-
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
Camel Quarkus AvroRpcTest requires quarkus.test.flat-class-path=true on Quarkus 2.0.0.Alpha3 #17463
Comments
The TCCL appears to be wrong, Jetty is using the base runtime CL rather than the runtime CL. I can't really see where Jetty is configured though. |
Thanks for the pointer, @stuartwdouglas . I'll try to dig deeper. |
@ppalaga @stuartwdouglas I tried some validations in debug mode and here are my results:
I see only one difference between Do you have an idea what could be wrong or what should I verify? EDITED: |
|
Problem is caused by https://github.com/eclipse/jetty.project/blob/jetty-9.4.x/jetty-util/src/main/java/org/eclipse/jetty/util/thread/QueuedThreadPool.java#L821 Both previous comments could be ignored. |
Issue is reported in jetty: jetty/jetty.project#6399 |
@JiriOndrusek @ppalaga is this issue still relevant? Linked GH issues are now resolved. |
I will check the issue tomorrow and let you know, whether it can be simulated with the current version of Quarkus. From the first (fast) glance at related tickets, there can not be a fix on jetty side. There are only some hints, how it could be solved on quarkus side - jetty/jetty.project#6399 (comment). |
I do not think that
AvroRpcTest
had an issue with Quarkus 2.0.0.Alpha1 and Quarkus 2.0.0.Alpha2. This issue seems to be new in Alpha3.Note that we have one more Avro test called
AvroTest
that requredquarkus.test.flat-class-path=true
on Alpha1 but was fixed in Alpha2 and also works on Alpha3.I did not have much time to investigate deeper. Here are the steps to reproduce and the symptoms:
Expected: the test should pass
Actual:
The text was updated successfully, but these errors were encountered: