Skip to content
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

Quartz dependency shouldn't start threads when it's not being used #4243

Closed
Sanne opened this issue Sep 27, 2019 · 0 comments · Fixed by #4554
Closed

Quartz dependency shouldn't start threads when it's not being used #4243

Sanne opened this issue Sep 27, 2019 · 0 comments · Fixed by #4554

Comments

@Sanne
Copy link
Member

@Sanne Sanne commented Sep 27, 2019

Describe the bug
For some reason an application I was profiling had the scheduler extension listed among its dependencies.

This was likely a mistake as there is nothing being scheduled.

Expected behavior
The extension should be "harmless"

Actual behavior
A couple of scheduling related threads are being initialized, and are running in background: stealing CPU time and memory from the main app.

Additional context
This clearly isn't critical, but considering we do several optimisations based on the "closed world assumption" I believe Quarkus should be able to enable the scheduler only if it's actually being used.

@mkouba mkouba added this to the 0.25.0 milestone Oct 15, 2019
@cescoffier cescoffier modified the milestones: 0.25.0, 0.26.0 Oct 15, 2019
@gsmet gsmet closed this in #4554 Oct 15, 2019
CSTDev added a commit to CSTDev/quarkus that referenced this issue Oct 22, 2019
dufoli pushed a commit to dufoli/quarkus that referenced this issue Oct 23, 2019
vsevel added a commit to vsevel/quarkus that referenced this issue Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.