[
https://issues.apache.org/jira/browse/TS-4750?focusedWorklogId=26680&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26680
]
ASF GitHub Bot logged work on TS-4750:
--------------------------------------
Author: ASF GitHub Bot
Created on: 19/Aug/16 22:58
Start Date: 19/Aug/16 22:58
Worklog Time Spent: 10m
Work Description: Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/pull/863
@oknet True there are many variants of the get_remote_* get_remote_ip
should be going away since it is IPv4 (looks like only two references remain).
For get_remote_endpoint and get_remote_addr really they are two versions
returning different data types. Some places it is more convenient to have an
Endpoint class other places we need a struct sockaddr. Since one calls the
other at least we don't have parallel implementations.
Issue Time Tracking
-------------------
Worklog Id: (was: 26680)
Time Spent: 1h 50m (was: 1h 40m)
> 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
> Fix For: 7.0.0
>
> Time Spent: 1h 50m
> 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)
