httpclient sockets stuck in CLOSE_WAIT

[Spencer Thomas]

For me, when I run into this sort of thing, tcpdump plus WireShark are my friends to see the actual details of the interchange.  Maybe Paul has done this.

On 6/30/20, 4:14 PM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

    On 6/30/20, 3:50 PM, "users on behalf of Paul B. Henson" <users-bounces at shibboleth.net on behalf of henson at cpp.edu> wrote:
    
    > I don't really understand the analysis in the idp ticket. The ticket seems to be blaming the network for this issue? That
    > doesn't sound correct, a socket stuck in CLOSE_WAIT is the fault of the application, not the network:
    
    I have no issues with sockets exhausting with my HTTP calls hanging that I have ever observed. That says to me it's not an inherent issue with the code, which leaves the network or other components as a trigger for the client to misbehave, if that is in fact what that means. That was the point being made; if it were an inherent issue with the client not closing connections, it would be trivially observable. Since we don't even do the closing, that really doesn't leave anything to try.
    
    The version of the HttpClient in 3.4+ is the only one that's ever been stable for me. The older ones were definitely unreliable at connection handling. But nothing since.
    
    -- Scott
    
    
    -- 
    For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
    To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net