You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2015/09/10 17:02:45 UTC
[jira] [Created] (TS-3901) Leaking connections from
HttpSessionManager
Susan Hinrichs created TS-3901:
----------------------------------
Summary: Leaking connections from HttpSessionManager
Key: TS-3901
URL: https://issues.apache.org/jira/browse/TS-3901
Project: Traffic Server
Issue Type: Bug
Components: HTTP
Reporter: Susan Hinrichs
Observed in production. Got the following warnings in diags.log
"Connection leak from http keep-alive system"
Our connections to origin would increase and the number of connections in CLOSE_WAIT were enormous.
I think the issue was when the origin URL was http with default port. That URL was remapped to https with default port. The default port stored in HttpServerSession->server_ip was not updated.
When the connection was closed or timed out of the session pool, it would be looked up with port 443. But the session was stored via the server_ip value with port 80 and would never match.
Relatively small change in HTTPHdr::_file_target_cache.
Running the fix in production to verify early results.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)