Skip to content

Conversation

@htztomic
Copy link
Contributor

This is a fix to GitHub issue #5314 which allows for configuration of Jetty's default thread pool, QueuedThreadPool, via the environment. Updated server properties are to include maxThreads, minThreads, and idleTimeout.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 14, 2019
/**
* Maximum amount of threads.
*/
private Integer maxThreads = 200;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would not be better to set the maximum number of threads based on the number of available cores?

Copy link
Member

@snicoll snicoll Aug 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The values here are the default of the embedded servers and we don't deviate from that unless necessary. If you want to pursue this idea, I'd raise an issue against the Jetty project.

@mbhave mbhave added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Aug 15, 2019
@mbhave mbhave modified the milestones: 2.2.x, 2.2.0.M6 Aug 15, 2019
mbhave pushed a commit that referenced this pull request Aug 16, 2019
mbhave added a commit that referenced this pull request Aug 16, 2019
@mbhave mbhave closed this in b853dff Aug 16, 2019
@mbhave mbhave changed the title Additional server properties added for Jetty Allow Jetty's threadpool to be configured via properties Aug 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants