[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
"\{clientType}.ActiveSessions" metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800 and local port 1024
3) Start jdbc or thin client with connecting to proxy server
{code:java}
ClientConfiguration cfg = new
ClientConfiguration().setAddresses("127.0.0.1:1024");
IgniteClient igniteClient = Ignition.startClient(cfg);
IgniteClient igniteClient2 = Ignition.startClient(cfg); {code}
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
"\{clientType}.ActiveSessions" metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> "\{clientType}.ActiveSessions" metrics no decrease in case when we use
> thin/jdbc client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
>
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800 and local port 1024
> 3) Start jdbc or thin client with connecting to proxy server
> {code:java}
> ClientConfiguration cfg = new
> ClientConfiguration().setAddresses("127.0.0.1:1024");
> IgniteClient igniteClient = Ignition.startClient(cfg);
> IgniteClient igniteClient2 = Ignition.startClient(cfg); {code}
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType\}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster. Although the
"ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics
are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy
server for remote port 10800 3) Start jdbc or thin client with connecting to
proxy server 4) Check "\\{clientType}
.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
\\{clientType\}.ActiveSessions metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType\}.ActiveSessions metrics no decrease in case when we use
> thin/jdbc client with proxy or vpn connection to cluster. Although the
> "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics
> are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy
> server for remote port 10800 3) Start jdbc or thin client with connecting to
> proxy server 4) Check "\\{clientType}
> .ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
"\{clientType}.ActiveSessions" metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType\}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster. Although the
"ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics
are updated correctly. Steps to reproduce: 1) Start Cluster 2) Start Proxy
server for remote port 10800 3) Start jdbc or thin client with connecting to
proxy server 4) Check "\\{clientType}
.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> "\{clientType}.ActiveSessions" metrics no decrease in case when we use
> thin/jdbc client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
"\{clientType}.ActiveSessions" metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
"\{clientType}.ActiveSessions" metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> "\{clientType}.ActiveSessions" metrics no decrease in case when we use
> thin/jdbc client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
>
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}
.ActiveSessions metrics no decrease in case when we use thin/jdbc client with
proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
>
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions
metrics no decrease in case when we use thin/jdbc client with proxy or vpn
connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions
> metrics no decrease in case when we use thin/jdbc client with proxy or vpn
> connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
>
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}
.ActiveSessions metrics no decrease in case when we use thin/jdbc client with
proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}
> .ActiveSessions metrics no decrease in case when we use thin/jdbc client with
> proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
>
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
_{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster._
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
\\{clientType\}.ActiveSessions metrics no decrease in case when we use
thin/jdbc client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions
metrics no decrease in case when we use thin/jdbc client with proxy or vpn
connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> \\{clientType\}.ActiveSessions metrics no decrease in case when we use
> thin/jdbc client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
>
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}
.ActiveSessions metrics no decrease in case when we use thin/jdbc client with
proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
_{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster._
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> _{clientType}.ActiveSessions metrics no decrease in case when we use
> thin/jdbc client with proxy or vpn connection to cluster._
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.Although the
"ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics
are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.Although the
> "ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics
> are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.Although the
"ClientListenerProcessor.Connections" and "views.CLIENT_CONNECTIONS" metrics
are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}
.ActiveSessions metrics no decrease in case when we use thin/jdbc client with
proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
We will still see one connection in "\{clientType}.ActiveSessions" and no
connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
still see one connection in "\{clientType}.ActiveSessions" and no connection in
"views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}
> .ActiveSessions metrics no decrease in case when we use thin/jdbc client with
> proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Attachment: ProxyServer.java
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}
> .ActiveSessions metrics no decrease in case when we use thin/jdbc client with
> proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS".
> We will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
still see one connection in "\{clientType}.ActiveSessions" and no connection in
"views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "
{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see
one connection in "\{clientType}
.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will still see one connection in "\{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "
{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still see
one connection in "\{clientType}
.ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
still see one connection in "{clientType}.ActiveSessions" and no connection in
"views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "\{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "
> {clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will still
> see one connection in "\{clientType}
> .ActiveSessions" and no connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17554) {clientType}.ActiveSessions metrics no decrease in case of connection through proxy/vpn
[
https://issues.apache.org/jira/browse/IGNITE-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepanov Ilya updated IGNITE-17554:
---
Description:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
still see one connection in "{clientType}.ActiveSessions" and no connection in
"views.CLIENT_CONNECTIONS".
was:
{clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
client with proxy or vpn connection to cluster.
Although the "ClientListenerProcessor.Connections" and
"views.CLIENT_CONNECTIONS" metrics are updated correctly.
Steps to reproduce:
1) Start Cluster
2) Start Proxy server for remote port 10800
3) Start jdbc or thin client with connecting to proxy server
4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
see one connection.
5) Stop jdbc or thin client
6) Stop Proxy server
7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We will
still see one connection in "{clientType}.ActiveSessions" and no connection in
"views.CLIENT_CONNECTIONS".
> {clientType}.ActiveSessions metrics no decrease in case of connection through
> proxy/vpn
> ---
>
> Key: IGNITE-17554
> URL: https://issues.apache.org/jira/browse/IGNITE-17554
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Stepanov Ilya
>Priority: Minor
> Labels: ise
> Attachments: ProxyServer.java
>
>
> {clientType}.ActiveSessions metrics no decrease in case when we use thin/jdbc
> client with proxy or vpn connection to cluster.
> Although the "ClientListenerProcessor.Connections" and
> "views.CLIENT_CONNECTIONS" metrics are updated correctly.
> Steps to reproduce:
> 1) Start Cluster
> 2) Start Proxy server for remote port 10800
> 3) Start jdbc or thin client with connecting to proxy server
> 4) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will see one connection.
> 5) Stop jdbc or thin client
> 6) Stop Proxy server
> 7) Check "{clientType}.ActiveSessions" and "views.CLIENT_CONNECTIONS". We
> will still see one connection in "{clientType}.ActiveSessions" and no
> connection in "views.CLIENT_CONNECTIONS".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
