-
Notifications
You must be signed in to change notification settings - Fork 812
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
HTTP Check and TCP checks will fail on windows #632
Comments
Another alternative is to actual spawn multiple processes per daemon instead of threads, using the |
Would need some time as it seems that multi processing windows services is not trivial: |
Is the patch merged into the mainline 2.7? Seems like it should be if the report was 2 years ago. But I can't really tell. |
Looks like it was released in 2.7.2 so as long as we're packaging a version >= 2.7.2 we should be okay. |
Going to make a quick fix for this one and file another issue to switch to multiprocessing |
If only on instance is configured because of the hard limit in the number of threads that is reached because windows agent run in separate threads and not in separate processes.
To Fix: Just add more flexibility in the thread limit for windows.
The text was updated successfully, but these errors were encountered: