[jira] [Updated] (TS-4187) connections_currently_open stat not accurate with global server session pools
[ https://issues.apache.org/jira/browse/TS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4187: -- Backport to Version: (was: 6.1.2) > connections_currently_open stat not accurate with global server session pools > - > > Key: TS-4187 > URL: https://issues.apache.org/jira/browse/TS-4187 > Project: Traffic Server > Issue Type: Bug >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 6.2.0, 7.0.0 > > > When global server session pools are used, sockets may be moved to new VCs > associated with different threads. The connections_currently_open stat was > not being correctly incremented in that case meaning the > connections_currently_open stat would go negative. > This means that the connection throttling logic would likely not trigger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4187) connections_currently_open stat not accurate with global server session pools
[ https://issues.apache.org/jira/browse/TS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4187: Backport to Version: 6.1.2 (was: 6.1.2, 6.2.0) > connections_currently_open stat not accurate with global server session pools > - > > Key: TS-4187 > URL: https://issues.apache.org/jira/browse/TS-4187 > Project: Traffic Server > Issue Type: Bug >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 6.2.0, 7.0.0 > > > When global server session pools are used, sockets may be moved to new VCs > associated with different threads. The connections_currently_open stat was > not being correctly incremented in that case meaning the > connections_currently_open stat would go negative. > This means that the connection throttling logic would likely not trigger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4187) connections_currently_open stat not accurate with global server session pools
[ https://issues.apache.org/jira/browse/TS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-4187: Fix Version/s: 6.2.0 > connections_currently_open stat not accurate with global server session pools > - > > Key: TS-4187 > URL: https://issues.apache.org/jira/browse/TS-4187 > Project: Traffic Server > Issue Type: Bug >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 6.2.0, 7.0.0 > > > When global server session pools are used, sockets may be moved to new VCs > associated with different threads. The connections_currently_open stat was > not being correctly incremented in that case meaning the > connections_currently_open stat would go negative. > This means that the connection throttling logic would likely not trigger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4187) connections_currently_open stat not accurate with global server session pools
[ https://issues.apache.org/jira/browse/TS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-4187: --- Backport to Version: 6.1.2, 6.2.0 (was: 6.1.2) Fix Version/s: (was: 6.2.0) 7.0.0 > connections_currently_open stat not accurate with global server session pools > - > > Key: TS-4187 > URL: https://issues.apache.org/jira/browse/TS-4187 > Project: Traffic Server > Issue Type: Bug >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 7.0.0 > > > When global server session pools are used, sockets may be moved to new VCs > associated with different threads. The connections_currently_open stat was > not being correctly incremented in that case meaning the > connections_currently_open stat would go negative. > This means that the connection throttling logic would likely not trigger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4187) connections_currently_open stat not accurate with global server session pools
[ https://issues.apache.org/jira/browse/TS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4187: -- Backport to Version: 6.1.2 > connections_currently_open stat not accurate with global server session pools > - > > Key: TS-4187 > URL: https://issues.apache.org/jira/browse/TS-4187 > Project: Traffic Server > Issue Type: Bug >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 6.2.0 > > > When global server session pools are used, sockets may be moved to new VCs > associated with different threads. The connections_currently_open stat was > not being correctly incremented in that case meaning the > connections_currently_open stat would go negative. > This means that the connection throttling logic would likely not trigger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4187) connections_currently_open stat not accurate with global server session pools
[ https://issues.apache.org/jira/browse/TS-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4187: -- Fix Version/s: 6.2.0 > connections_currently_open stat not accurate with global server session pools > - > > Key: TS-4187 > URL: https://issues.apache.org/jira/browse/TS-4187 > Project: Traffic Server > Issue Type: Bug >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 6.2.0 > > > When global server session pools are used, sockets may be moved to new VCs > associated with different threads. The connections_currently_open stat was > not being correctly incremented in that case meaning the > connections_currently_open stat would go negative. > This means that the connection throttling logic would likely not trigger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
