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

connection_type == worker causes connection failure #1513

Open
okeuday opened this issue Apr 22, 2021 · 2 comments
Open

connection_type == worker causes connection failure #1513

okeuday opened this issue Apr 22, 2021 · 2 comments

Comments

@okeuday
Copy link
Contributor

okeuday commented Apr 22, 2021

Currently, if HTTP/1.1 is used with a cowboy connection that has been configured with connection_type == worker, the first request will succeed with the connection and a second request performed immediately will fail. If that should not occur, it appears like source code would need to change, so currently connection_type must always be supervisor, right? Is there a way to use connection_type == worker now that isn't documented?

@essen
Copy link
Member

essen commented Apr 22, 2021

It's only been tested with supervisor connection type. To allow setting it to worker we would need to disable spawning of processes, and supposedly fix the error you got. A stacktrace or other would be helpful.

@okeuday
Copy link
Contributor Author

okeuday commented Apr 23, 2021

No stacktrace went to the Erlang/OTP kernel logger for the problem. Only got a timeout from the HTTP client on the second request. Was using current cowboy master, current cowlib master, ranch 2.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants