[
https://issues.apache.org/jira/browse/TS-4750?focusedWorklogId=26492&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26492
]
ASF GitHub Bot logged work on TS-4750:
--------------------------------------
Author: ASF GitHub Bot
Created on: 16/Aug/16 04:00
Start Date: 16/Aug/16 04:00
Worklog Time Spent: 10m
Work Description: Github user oknet commented on the issue:
https://github.com/apache/trafficserver/pull/863
@zwoop Looks good to me!
@shinrich we are defined too many get_remote_*() method, my suggest is only
keep one from get_remote_addr() and get_remote_endpoint()
Issue Time Tracking
-------------------
Worklog Id: (was: 26492)
Time Spent: 1h 20m (was: 1h 10m)
> 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: 1h 20m
> 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)
