You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/10/07 19:36:20 UTC

[jira] [Resolved] (TS-4893) Leaking H2 connections

     [ https://issues.apache.org/jira/browse/TS-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom resolved TS-4893.
-------------------------------
    Resolution: Duplicate

> Leaking H2 connections
> ----------------------
>
>                 Key: TS-4893
>                 URL: https://issues.apache.org/jira/browse/TS-4893
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP/2, Network
>            Reporter: Leif Hedstrom
>
> On Docs, I'm seeing e.g. this:
> {code}
> [TS_MAIN] 1728 nobody   52u     IPv4         1548184130      0t0        TCP qa1:https->unknown.servercentral.net:60107 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   53u     IPv4         1517137327      0t0        TCP qa1:https->msnbot-157-55-39-245.search.msn.com:18649 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   54u     IPv4         1547299121      0t0        TCP qa1:https->unknown.servercentral.net:54210 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   55u     IPv4         1546653567      0t0        TCP qa1:https->unknown.servercentral.net:38563 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   56u      REG              202,1     2907    1711981 /opt/ats/var/log/trafficserver/error.log
> [TS_MAIN] 1728 nobody   57u     IPv4         1547305120      0t0        TCP qa1:https->unknown.servercentral.net:54558 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   58u     IPv4         1546341443      0t0        TCP qa1:https->unknown.servercentral.net:45169 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   59u     IPv4         1548496071      0t0        TCP qa1:https->unknown.servercentral.net:45723 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   60u     IPv4         1585632811      0t0        TCP qa1:https->183.240.202.49:31756 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   61u     IPv4         1565899597      0t0        TCP qa1:https->unknown.servercentral.net:56875 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   62u     IPv4         1566772178      0t0        TCP qa1:https->unknown.servercentral.net:52435 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   63u     IPv4         1567423730      0t0        TCP qa1:https->unknown.servercentral.net:44075 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   64u     IPv4         1585491833      0t0        TCP qa1:https->c-73-181-14-238.hsd1.co.comcast.net:62420 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   65u     IPv4         1566460810      0t0        TCP qa1:https->unknown.servercentral.net:39178 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   66u     IPv4         1585625076      0t0        TCP qa1:https->143.37.120.106.static.bjtelecom.net:61392 (ESTABLISHED)
> [TS_MAIN] 1728 nobody   68u     IPv4         1585680362      0t0        TCP qa1:52297->192.168.3.1:acmsoda (ESTABLISHED)
> [TS_MAIN] 1728 nobody   73u     IPv4         1585595085      0t0        TCP qa1:https->89.25.14.226:36281 (ESTABLISHED)
> {code}
> These do generally not seem to clear. At the same time as this was captured, I checked the metrics for client connections, and there were none reported by ATS. This might be related to TS-4833, and perhaps TS-4892.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)