You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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.
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:
and soon enough all but one will hang with:
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.
The text was updated successfully, but these errors were encountered: