[JBoss JIRA] (WFLY-6583) Session leak on SmartOS hosts
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-6583?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-6583:
------------------------------------
The active-sessions metric uses the SessionManager.getActiveSessions() method - which for a distributed session manager will return the identifiers of the sessions residing in memory (excluding passivated sessions) on the node. If the SessionManager is backed by a distributed cache (as is the case with the default configuration), this will include sessions owned by the target node, as well as sessions for which the target node is a backup. For a cluster size of 3, where each node has just created N sessions, the value for active-sessions would return, on average, 2*N (i.e. N local sessions plus N/2 sessions for each remote node). Likewise, if the SessionManager is backed by a replicated cache, the active-sessions metric would return 3*N (i.e. N local sessions, plus N sessions for each remote node). You can see why I am cautious about drawing premature conclusions from this mechanism of measuring the number of sessions.
> Session leak on SmartOS hosts
> -----------------------------
>
> Key: WFLY-6583
> URL: https://issues.jboss.org/browse/WFLY-6583
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.2.0.Final, 9.0.0.Final, 10.0.0.Final
> Environment: CentOS 7 or SmartOS instance using Joyents Infrastructure/Bare metal container.
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# java -version
> java version "1.8.0_77"
> Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# uname -a
> Linux 979638eb-b45c-45b3-9fdb-d7f48276e4ef 3.10.0 BrandZ virtual linux x86_64 x86_64 x86_64 GNU/Linux
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# cat /etc/issue
> \S
> Kernel \r on an \m
> Reporter: Michael Noack
> Assignee: Paul Ferraro
> Priority: Minor
>
> When running Wildfly 8.2.0-Final, 9.0.0-Final or 10.0.0-Final in domain mode using the full-ha profile some sessions never get closed when running on SmartOS or a BrandZ kernel on SmartOS. The amount of unclosed sessions rises slowly. With 1 session per second and server created, roughly 30-50 sessions are left unclosed on each server. I've been keeping track of this issue for almost a year now and handled it by restarting the entire cluster at first. It took me a while to connect the dots here.
> When registering a HttpSessionListener and logging any sessionCreated(HttpSessionEvent se) and sessionDestroyed(HttpSessionEvent se) one can cleary see some sessions never generate the sessionDestroyed event.
> The problem disappears when running the very same setup on a KVM instance of CentOS 6 or 7 (regardless whether the KVM host is SmartOS or Linux).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFCORE-1525) ageout-history does not report failures
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1525?page=com.atlassian.jira.plugi... ]
Bartosz Spyrko-Śmietanko moved WFLY-6572 to WFCORE-1525:
--------------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1525 (was: WFLY-6572)
Component/s: Patching
(was: Patching)
Affects Version/s: 2.1.0.Final
(was: 10.0.0.Final)
> ageout-history does not report failures
> ----------------------------------------
>
> Key: WFCORE-1525
> URL: https://issues.jboss.org/browse/WFCORE-1525
> Project: WildFly Core
> Issue Type: Bug
> Components: Patching
> Affects Versions: 2.1.0.Final
> Reporter: Dennis Reed
> Assignee: Bartosz Spyrko-Śmietanko
>
> When ageout-history cannot delete the old CP files, it silently fails and returns "success".
> LocalAgeoutHistoryHandler#recursiveDelete does keep track of whether the
> delete failed or succeeded, but the return value from this method is ignored
> in execute(...).
> If recursiveDelete returns false, it should report a failure.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFLY-6572) ageout-history does not report failures
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/WFLY-6572?page=com.atlassian.jira.plugin.... ]
Bartosz Spyrko-Śmietanko updated WFLY-6572:
-------------------------------------------
Component/s: Patching
> ageout-history does not report failures
> ----------------------------------------
>
> Key: WFLY-6572
> URL: https://issues.jboss.org/browse/WFLY-6572
> Project: WildFly
> Issue Type: Bug
> Components: Patching
> Affects Versions: 10.0.0.Final
> Reporter: Dennis Reed
> Assignee: Bartosz Spyrko-Śmietanko
>
> When ageout-history cannot delete the old CP files, it silently fails and returns "success".
> LocalAgeoutHistoryHandler#recursiveDelete does keep track of whether the
> delete failed or succeeded, but the return value from this method is ignored
> in execute(...).
> If recursiveDelete returns false, it should report a failure.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFLY-6583) Session leak on SmartOS hosts
by Michael Noack (JIRA)
[ https://issues.jboss.org/browse/WFLY-6583?page=com.atlassian.jira.plugin.... ]
Michael Noack updated WFLY-6583:
--------------------------------
Steps to Reproduce:
Spin up any 3 SmartOS or Infrastructure Container instances on Joyent cloud service (or install SmartOS on 3 physical devices). For reference I will call those server 1, 2 and 3.
Install JDK 7 or 8 (8 required for 10.0.0) on all of them.
Deploy wildfly-10.0.0-Final to all three instances and follow the clustering guide.
I made server 1 the DC without any servers being specified in host.xml
I used the following type of servers on server 2+3:
<servers>
<server name="slave64-server-210" group="server-group-b" auto-start="true">
<socket-bindings port-offset="210"/>
</server>
</servers>
Deploy any clusterized webapp, I used our production app as well as https://github.com/liweinan/cluster-demo for tests, the app doesn't matter
Repeatedly call any webapp uri that creates a session, for example using:
wget http://$server:8290/cluster-demo/index.jsp -O status.$server -q -o /dev/null
Monitor the session count of the deployment on both servers, example:
/opt/wildfly/bin/./jboss-cli.sh --connect --user="username" --password="password" --command="/host=slave2/server=slave2-server-210/deployment=cluster-demo.war/subsystem=undertow :read-attribute(name=active-sessions)
was:
Spin up any 3 SmartOS or Infrastructure Container instances on Joyent cloud service (or install SmartOS on 3 physical devices). For reference I will call those server 1, 2 and 3.
Install JDK 7 or 8 (8 required for 10.0.0) on all of them.
Deploy wildfly-10.0.0-Final to all three instances and follow the clustering guide.
I made server 1 the DC without any servers being specified in host.xml
I used the following type of servers on server 2+3:
<servers>
<server name="slave64-server-210" group="server-group-b" auto-start="true">
<socket-bindings port-offset="210"/>
</server>
</servers>
Deploy any clusterized webapp, I used our production app as well as https://github.com/liweinan/cluster-demo for tests, the app doesn't matter
Repeatedly call any webapp uri that creates a session, for example using:
wget http://$server:8290/cluster-demo/index.jsp -O status.$server -q -o /dev/null
Monitor the session count of the deployment on both servers, example:
/opt/wildfly/bin/./jboss-cli.sh --connect --user="password" --password="username" --command="/host=slave2/server=slave2-server-210/deployment=cluster-demo.war/subsystem=undertow :read-attribute(name=active-sessions)
> Session leak on SmartOS hosts
> -----------------------------
>
> Key: WFLY-6583
> URL: https://issues.jboss.org/browse/WFLY-6583
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.2.0.Final, 9.0.0.Final, 10.0.0.Final
> Environment: CentOS 7 or SmartOS instance using Joyents Infrastructure/Bare metal container.
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# java -version
> java version "1.8.0_77"
> Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# uname -a
> Linux 979638eb-b45c-45b3-9fdb-d7f48276e4ef 3.10.0 BrandZ virtual linux x86_64 x86_64 x86_64 GNU/Linux
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# cat /etc/issue
> \S
> Kernel \r on an \m
> Reporter: Michael Noack
> Assignee: Paul Ferraro
> Priority: Minor
>
> When running Wildfly 8.2.0-Final, 9.0.0-Final or 10.0.0-Final in domain mode using the full-ha profile some sessions never get closed when running on SmartOS or a BrandZ kernel on SmartOS. The amount of unclosed sessions rises slowly. With 1 session per second and server created, roughly 30-50 sessions are left unclosed on each server. I've been keeping track of this issue for almost a year now and handled it by restarting the entire cluster at first. It took me a while to connect the dots here.
> When registering a HttpSessionListener and logging any sessionCreated(HttpSessionEvent se) and sessionDestroyed(HttpSessionEvent se) one can cleary see some sessions never generate the sessionDestroyed event.
> The problem disappears when running the very same setup on a KVM instance of CentOS 6 or 7 (regardless whether the KVM host is SmartOS or Linux).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFLY-6583) Session leak on SmartOS hosts
by Michael Noack (JIRA)
[ https://issues.jboss.org/browse/WFLY-6583?page=com.atlassian.jira.plugin.... ]
Michael Noack edited comment on WFLY-6583 at 5/4/16 11:39 AM:
--------------------------------------------------------------
Sure:
/opt/wildfly/bin/./jboss-cli.sh --connect --user="username" --password="password" --command="/host=slave2/server=slave2-server-210/deployment=cluster-demo.war/subsystem=undertow :read-attribute(name=active-sessions)
was (Author: michael.noack):
Sure:
/opt/wildfly/bin/./jboss-cli.sh --connect --user="password" --password="username" --command="/host=slave2/server=slave2-server-210/deployment=cluster-demo.war/subsystem=undertow :read-attribute(name=active-sessions)
> Session leak on SmartOS hosts
> -----------------------------
>
> Key: WFLY-6583
> URL: https://issues.jboss.org/browse/WFLY-6583
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.2.0.Final, 9.0.0.Final, 10.0.0.Final
> Environment: CentOS 7 or SmartOS instance using Joyents Infrastructure/Bare metal container.
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# java -version
> java version "1.8.0_77"
> Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# uname -a
> Linux 979638eb-b45c-45b3-9fdb-d7f48276e4ef 3.10.0 BrandZ virtual linux x86_64 x86_64 x86_64 GNU/Linux
> [root@979638eb-b45c-45b3-9fdb-d7f48276e4ef /]# cat /etc/issue
> \S
> Kernel \r on an \m
> Reporter: Michael Noack
> Assignee: Paul Ferraro
> Priority: Minor
>
> When running Wildfly 8.2.0-Final, 9.0.0-Final or 10.0.0-Final in domain mode using the full-ha profile some sessions never get closed when running on SmartOS or a BrandZ kernel on SmartOS. The amount of unclosed sessions rises slowly. With 1 session per second and server created, roughly 30-50 sessions are left unclosed on each server. I've been keeping track of this issue for almost a year now and handled it by restarting the entire cluster at first. It took me a while to connect the dots here.
> When registering a HttpSessionListener and logging any sessionCreated(HttpSessionEvent se) and sessionDestroyed(HttpSessionEvent se) one can cleary see some sessions never generate the sessionDestroyed event.
> The problem disappears when running the very same setup on a KVM instance of CentOS 6 or 7 (regardless whether the KVM host is SmartOS or Linux).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month
[JBoss JIRA] (WFLY-6362) Refactor the god class JBossServiceXmlDescriptorParser
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-6362?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-6362.
----------------------------
Resolution: Won't Fix
Closing since it doesn't seem to add anything. If there had been a PR it could maybe have been merged.
> Refactor the god class JBossServiceXmlDescriptorParser
> ------------------------------------------------------
>
> Key: WFLY-6362
> URL: https://issues.jboss.org/browse/WFLY-6362
> Project: WildFly
> Issue Type: Enhancement
> Components: JMX
> Reporter: Shishir Subramanyam
> Assignee: Kabir Khan
> Priority: Trivial
>
> Refactor the classes JBossServiceXmlDescriptorParser and JBossServiceConfig from SAR by adding a parametized constructor for JBossServiceConfig. This is done so that JBossServiceXmlDescriptorParser does not call multiple set methods for each attribute while returning an object of JBossServiceConfig in the method parseMBean and uses the parametized constructor instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 1 month