-
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
Native TS: integration-tests/quartz leaves hanging processes #28114
Labels
Milestone
Comments
quarkus-bot
bot
added
area/kotlin
area/kubernetes
area/mandrel
area/scheduler
area/securepipeline
issues related to ensure Quarkus can be used in a secure pipeline setups like FIPS or similar
labels
Sep 21, 2022
/cc @Sgitario, @evanchooly, @galderz, @geoand, @iocanel, @jerboaa, @machi1990, @mkouba, @zakkak |
Karm
changed the title
Native test suite, Builder image: integration-tests/quartz leaves hanging processes
Native TS: integration-tests/quartz leaves hanging processes
Sep 21, 2022
Karm
removed
area/kotlin
area/kubernetes
area/securepipeline
issues related to ensure Quarkus can be used in a secure pipeline setups like FIPS or similar
labels
Sep 21, 2022
I can confirm I see this. I'll check and see what is going on |
#28118 takes care of it |
I can reproduce it with the current main on my workstation too as:
|
Yup, there was an oversight in the test framework |
😆 |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 21, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a certain amount of time for the scheduler to shutdown. Relates to quarkusio#28114
#28119 is also related |
geoand
added a commit
that referenced
this issue
Sep 21, 2022
Ensure that @QuarkusIntegrationTest does not leave dangling processes
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 23, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 23, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 23, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 26, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114 Co-authored-by: Manyanda Chitimbo <[email protected]>
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 26, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114 Co-authored-by: Manyanda Chitimbo <[email protected]>
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 26, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114 Co-authored-by: Manyanda Chitimbo <[email protected]>
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Oct 3, 2022
Fixes: quarkusio#28114 (cherry picked from commit 25cf7c6)
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114 Co-authored-by: Manyanda Chitimbo <[email protected]>
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114 Co-authored-by: Manyanda Chitimbo <[email protected]>
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 16, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114 Co-authored-by: Manyanda Chitimbo <[email protected]>
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 17, 2022
igorregis
pushed a commit
to igorregis/quarkus
that referenced
this issue
Oct 17, 2022
The Quartz scheduler shutdown seems like it can block indefinitely if there is an exception in a yet to be completed job. To guard against this, we ensure that we only wait a configurable amount of time for the scheduler to shut down. This is a breaking change because previously we waited indefinitely. Relates to quarkusio#28114 Co-authored-by: Manyanda Chitimbo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
It seems that the TS leaves hanging Quartz runner processes. At least when executed with builder image and in native mode. It becomes apparent on a system that is not re-provisioned for each TS run, e.g.:
The good new is the process survived since August. The bad news is that this should not be happening.
I will take a look at what the Quartz TS does and why this happens unless someone well versed in Quartz beats me to it.
Expected behavior
TS does not leave any hanging processes.
Actual behavior
Quartz native executable runner left.
How to Reproduce?
Output of
uname -a
orver
Linux amd64
Output of
java -version
Temurin-11.0.15+10
GraalVM version (if different from Java)
22.3 dev, Git head: 4407306f2505
Quarkus version or git rev
2.13.0.CR1, 2.7.6.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: