-
Notifications
You must be signed in to change notification settings - Fork 39
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
Connection error when sampling many URLs #20
Comments
In general there aren't any limitations on the number of connections. The error message indicates that the server refuses additional connections, although you mention that a different tool doesn't show this issues. Maybe there is a difference in connection reuse. I don't have a Window machine available for testing but will try to reproduce the issue with Linux. |
Thanks for the quick reply. |
Quick update: We upgraded our httpbeat to the latest version (4.0.0), and the problem persists. |
I just tried it with 100 connections and it runs without problems. |
Did you had a change to check it again? |
Hi,
We're using httpbeat to sample every minute (cron: "@every 1m") multiple URLs from http://127.0.0.1:8443 on a Windows 2012 R2 machine.
It works great for a list of a few URLs, but when we increase the list to around 30 URLs or more, we sometimes get this error in the LOG file:
It isn't a problem on the web server side, because the same sample of URLs with the same frequency works just fine using a different sampling tool.
Is there a limit to the number of URLs we can sample with one instance of httpbeat, or did we find a performance problem?
Please advise,
Eyal
The text was updated successfully, but these errors were encountered: