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
Intermittent failure of CamelDevModeTest #1468
Comments
Seems to be a race condition. Even with the guard it still fails occasionally. The Arc container must be getting nullified between firing the event and the Quarkus bits doing the |
I don't think this is fully fixed. I still see the occasional failure locally and the nightly quarkus-master sync job failed: |
Do you happen to have a stack trace at hand? |
One in how many failures do you see locally? |
I am running |
Seems it's the same issue.
I just ran the build and it failed on the first try. The same thing happened yesterday. Like I said in our chat on Monday, Quarkus shutdown tasks are executed in reverse order to which they were added. The Arc shutdown task is added after Camel's, so it runs first. I'm not sure whether the current solution of awaiting camel shutdown actually helps much, because the Arc container shutdown will already be in progress (I think). |
Just to make sure: the name of the thread throwing the exception is |
Yes - seems so. |
we can disable firing the shutdown events till we have a clear solution, there is still an option to register an handler that does not depend on CDI so if that's really needed, we have a workaround |
There are two shutdown tasks added by
I can see the following (IMO correct) ordering of the tasks on shutdown:
|
I think I know what is the problem. My fix is flawed. Calling |
@ppalaga as |
Sorry, I meant |
Seems
CamelMainEventBridge
fires events after Quarkus is shutdown and thus the Arc container isnull
. HenceIllegalArgumentException
is thrown here.The text was updated successfully, but these errors were encountered: