[
https://issues.apache.org/jira/browse/TS-4750?focusedWorklogId=26389&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26389
]
ASF GitHub Bot logged work on TS-4750:
--------------------------------------
Author: ASF GitHub Bot
Created on: 12/Aug/16 21:24
Start Date: 12/Aug/16 21:24
Worklog Time Spent: 10m
Work Description: GitHub user shinrich opened a pull request:
https://github.com/apache/trafficserver/pull/863
TS-4750: Fix Connection Leak warnings.
Removing secondary server address cache in HttpServerSession. Instead pull
that information from netvc. Use the same address to add server sessions to
cache to and remove server sessions from cache.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shinrich/trafficserver ts-4750
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/863.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #863
----
commit e5a919c654cef0e3058c10f76d897ef028130fa4
Author: Susan Hinrichs <[email protected]>
Date: 2016-08-12T20:53:41Z
TS-4750: Fix Connection Leak warnings.
----
Issue Time Tracking
-------------------
Worklog Id: (was: 26389)
Time Spent: 10m
Remaining Estimate: 0h
> Erroneous WARNING: Connection leak from http keep-alive system
> --------------------------------------------------------------
>
> Key: TS-4750
> URL: https://issues.apache.org/jira/browse/TS-4750
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We saw this a while back, but didn't get the fix pushed to open source. It
> looks like the issue is still present in the current master.
> HttpSessionManager caches the server address, but that cached address drifts
> from the get_remote_addr() in the vc associated with the cached server
> session. The problem is that one value is used to put the session into the
> hash table, but the other value is used to remove the session from the hash
> table later. So the session gets lost in the hash table. The session is not
> found and the connection leak warning message is generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
