Bug 5488 - vsmserver should limit the number of concurrent jobs by having a queue of jobs to be done
Summary: vsmserver should limit the number of concurrent jobs by having a queue of job...
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: 2.0.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Henrik Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-07 12:13 CEST by Karl Mikaelsson
Modified: 2015-04-14 10:32 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Karl Mikaelsson cendio 2015-04-07 12:13:01 CEST 
Right now, vsmserver just launches all jobs (session verifications, etc) that it has received/scheduled right away, with no regard to any limits. We've seen that both low ports (bug 217) and file descriptors (bug 5442) has run out, leading to vsmserver crashes.

It would be beneficial if we could limit the amount of jobs running concurrently to less than the number required to crash. With a queue, we could also make sure that we don't overwhelm any agent server with too many requests.
Note You need to log in before you can comment on or make changes to this bug.