[jboss-jira] [JBoss JIRA] (WFLY-6583) Session leak on SmartOS hosts

[ https://issues.jboss.org/browse/WFLY-6583?page=com.atlassian.jira.plugin.... ] Michael Noack commented on WFLY-6583: ------------------------------------- [~ctomc] I've tried several jdks in the past for unrelated reason. In production we currently use: [root@0e231418-37b9-657f-ff45-a3b252c7f2da ~]# java -version openjdk version "1.7.0-internal" OpenJDK Runtime Environment (build 1.7.0-internal-pkgsrc_2015_04_23_11_23-b00) OpenJDK 64-Bit Server VM (build 24.76-b04, mixed mode) For tests with wildfly-10.0.0.Final I used (jdk-8u77-linux-x64.rpm from Oracle): [root@d9be4e60-9641-4be9-a552-e1d0d7315167 ~]# 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) [~pferraro] Thanks's for your reply. I'm well aware of this lack of a guarantee. Since I only used two servers in tests it was rather easy to take logs from both servers and look for matches in both logs at the same time. Also a session getting destroyed on another node wouldn't lead to an increasing amount of sessions on both nodes. This is confirmed by using a KVM container, where the amount of sessions on both nodes remains constant, as long as polling the web service is time constant. As soon as polling stops, the amount of sessions goes down again, until it eventually reaches 0 on both nodes. On a native container the amount of session will go down as well for as long as the timeout is, than stay at that level. I ran a 24h tests again from yesterday till today using a ten minutes timeout for sessions. After stopping the polling and waiting for 10 minutes, both nodes would have roughly 1300 sessions left. This amount hasn't changed since. I just checked the server again. No session has been created for the last 3-4 hours, and yet this is the result when queriing the nodes: { "outcome" => "success", "result" => 1348 } { "outcome" => "success", "result" => 1448 } Those are KVM images that don't display the problem: https://docs.joyent.com/public-cloud/instances/virtual-machines/images/li... Those are container native images using a BrandZ kernel with the issue: https://docs.joyent.com/public-cloud/instances/infrastructure/images/cent... I'm using the same rpm to install the jdk, and the wildfly nodes are in fact just copies of each other. The only configuration difference is for the interfaces ip adresses in host.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)