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

Lost connection? #43

Closed
gregw opened this issue May 11, 2017 · 1 comment
Closed

Lost connection? #43

gregw opened this issue May 11, 2017 · 1 comment

Comments

@gregw
Copy link
Contributor

gregw commented May 11, 2017

I'm using jnr-unix-socket in the jetty servlet container and am having problem with connect (see jetty/jetty.project#1281). In summary, if we have a multiple clients connecting at the same time, sometimes a connection attempt is lost and just hangs.

This can be demonstrated by having two or more shells executing the loop:

while :; do curl -v --unix-socket /tmp/jetty.sock http://localhost/ ; done

and soon enough all but one will hang with:

*   Trying /tmp/jetty.sock...

this is with 0.18. I've tried both blocking and async connections and I see the same result.

I've not yet nailed this down as a JNR bug and it is probably that there is something wrong in jetty's usage. But I thought I'd open this issue to see if you can shed any light on it. Meanwhile I will work on a minimal reproduction.

@gregw
Copy link
Contributor Author

gregw commented May 11, 2017

I'm going to close this for now, as I tried a simple reproduction based on your example code and it does not fail. I really can't see what Jetty is doing differently, but until I can prove otherwise I will assume it is either Jetty or curl. If you have any insights, please comment on the jetty issue.

@gregw gregw closed this as completed May 11, 2017
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

1 participant